unknow host error in docker about spring-cloud-microservice-example HOT 5 CLOSED

If I understand your problem correct, it has to do with the containerID which is used as hostname which is not known?

I had something similar: DiscoveryClient registered my Service at Consul (Eureka would probably do the same) and gave the container id of the service to register itself with. The healthcheck then failed because both Consul as my service ran in different containers and they didn't know eachother through container ID's. I could not find a way to configure the discovery client to use the IP address instead of the host name (container id?).

from spring-cloud-microservice-example.

See spring-cloud/spring-cloud-netflix#432

Also try using this configuration for your services that are registering with Eureka:

eureka.instance.preferIpAddress=true

This is documented here: https://github.com/spring-cloud/spring-cloud-netflix/blob/a7398842078319dcaa353a708c12bb7b9fa85a4e/docs/src/main/asciidoc/spring-cloud-netflix.adoc#prefer-ip-address

from spring-cloud-microservice-example.

Oh,I config it https://github.com/Dreampie/cloud-config-repo/blob/master/application.yml,always not work

eureka:
  password: eureka
  client:
    serviceUrl:
      defaultZone: ${EUREKA_SERVER_URL:http://user:${eureka.password}@192.168.60.41:8761/eureka/}
  instance:
    preferIpAddress: true
    leaseRenewalIntervalInSeconds: 10
    metadataMap:
      instanceId: ${EUREKA_INSTANCE_ID:${spring.application.name}:${spring.application.instance_id:${server.port:8080}}}

from spring-cloud-microservice-example.

@Dreampie You may want to consider adding a health indicator for your configuration service to make sure that the right config is being retrieved for your applications at startup: http://cloud.spring.io/spring-cloud-config/spring-cloud-config.html#_health_indicator

from spring-cloud-microservice-example.

thank you!

from spring-cloud-microservice-example.