Why do Spring Cloud Netflix applications deployed on Docker containers require explicitly setting eureka.instance.hostname? Why do Spring Cloud Netflix applications deployed on Docker containers require explicitly setting eureka.instance.hostname? docker docker

Why do Spring Cloud Netflix applications deployed on Docker containers require explicitly setting eureka.instance.hostname?


I believe each Docker container would need to register using the Docker host IP and Docker host port mapped to the container port.

This what I have used:

Eureka instance:

docker run -idt -p 8001:8001 --net=host -e spring.profiles.active=peerAware -e appPort=8001 -e hostName=$HOSTNAME -e dataCenter=asimio-cloud-dal -e environment=staging -e peerUrls="http://$HOSTNAME:8002/eureka/" asimio/discovery-server:1.0.73

A service instance:

docker run -idt -p 8601:8601 --net=host -e appPort=8601 -e hostName=$HOSTNAME -e eureka.client.serviceUrl.defaultZone="http://$HOSTNAME:8001/eureka/,http://$HOSTNAME:8002/eureka/" asimio/demo-registration-api-2:1.0.21

http://tech.asimio.net/2016/11/14/Microservices-Registration-and-Discovery-using-Spring-Cloud-Eureka-Ribbon-and-Feign.html#running-the-discovery-server-and-demo-services-in-docker-containers