具有Spring Boot的Docker和Eureka无法注册客户端(Docker and Eureka with Spring Boot failing to register clients)

 我有一个使用Spring Boot + Docker Compose + Eureka的非常简单的演示。 
 
 我的服务器在端口8671上运行，具有以下应用程序属性： 
 
server:
  port: 8761
eureka:
  instance:
    prefer-ip-address: true
  client:
    registerWithEureka: false
    fetchRegistry: false
  server:
    waitTimeInMsWhenSyncEmpty: 0
 
 我的Eureka客户端在端口9000上运行，具有以下应用程序属性： 
 
server:
  port: 9000
spring:
  application:
    name: user-registration
eureka:
  client:
    registerWithEureka: true
    fetchRegistry: true
    serviceUrl:
      defaultZone: http://localhost:8761/eureka/
  instance:
    prefer-ip-address: true
 
 当我在父maven项目中启动docker.compose文件时，这是我的docker-compose文件的内容： 
 
eureka-server:
  image: rosenthal/eureka-server
ports:
   - "8761:8761"
user-registration:
  image: rosenthal/user-registration
  ports:
   - "9000:9000"
  links:
   - eureka-server
 
 当我通过首先启动eureka服务器来运行我的应用程序时，由客户端通过 
 
mvn spring-boot:run 
 
 服务器成功注册我的客户端（我称之为用户注册）。 
 
 当我通过docker-compose运行我的应用程序时，客户端无法注册以下输出： 
 
 DiscoveryClient_USER-REGISTRATION/0fd640cbc3ba:user-registration:9000: 
 registering service...
 user-registration_1  | 2017-06-21 04:36:05.120 ERROR 1 --- [nfoReplicator-0]        
 c.n.d.s.t.d.RedirectingEurekaHttpClient  : Request execution error
 user-registration_1  | 
 user-registration_1  | com.sun.jersey.api.client.ClientHandlerException: 
 java.net.ConnectException: Connection refused (Connection refused)
 
 我的第一个假设是，在等待服务器启动时运行docker-compose遇到竞争条件，但是我的eureka客户端似乎有一个心跳试图回家到它配置的服务器。 这意味着它无法找到我已注册的Eureka服务器（并且正在运行，我可以在localhost：8671上导航到它）。 
 
 我在这里想念的是什么？ 一切都运行良好，本地运行spring-boot启动它自己的嵌入式tomcat容器。 一旦我开始用docker-compose做它，它就不想工作了。 
 
 编辑 
 
 我相信，我意识到了自己的问题。 所以docker不在localhost上运行，它在我启动docker时分配的公共IP上运行。 导航到此ip +端口显示我的服务正在运行Eureka Server。 客户仍然没有注册。 
 
 所以，我对我的eureka客户端的application.yml文件进行了更改： 
 
serviceUrl:
  defaultZone: http://192.168.59.103:8761/eureka/
 
 IP是我的docker守护程序运行的IP。 现在，当我做docker-compose时，它错过了第一次注册，但是第二次心跳接收了我的客户端。 
 
 如何确保客户端在服务器完全启动之前等待？ 我在我的docket compose文件中使用了正确的docker“links”字段，但它并没有像我希望的那样工作。 另外，如何将defaultZone文件视为我的DOCKER_HOST IP？ 
 
 最后结果 
 
 生成一切对我有用的生成的docker-compose文件是： 
 
eureka-server:
  image: thorrism/eureka-server
  ports:
   - "8761:8761"
user-registration:
  image: thorrism/user-registration
  ports:
   - "9000:9000"
  links:
   - eureka-server
  environment:
    EUREKA_CLIENT_SERVICEURL_DEFAULTZONE: http://eureka-server:8761/eureka

I have a very simple demo of using Spring Boot + Docker Compose + Eureka. 
 
My server runs on port 8671 with the following application properties:
 
server:
  port: 8761
eureka:
  instance:
    prefer-ip-address: true
  client:
    registerWithEureka: false
    fetchRegistry: false
  server:
    waitTimeInMsWhenSyncEmpty: 0
 
My Eureka client runs on port 9000 with the following application properties:
 
server:
  port: 9000
spring:
  application:
    name: user-registration
eureka:
  client:
    registerWithEureka: true
    fetchRegistry: true
    serviceUrl:
      defaultZone: http://localhost:8761/eureka/
  instance:
    prefer-ip-address: true
 
When I start up my docker.compose file in the parent maven project, this is the contents of my docker-compose file:
 
eureka-server:
  image: rosenthal/eureka-server
ports:
   - "8761:8761"
user-registration:
  image: rosenthal/user-registration
  ports:
   - "9000:9000"
  links:
   - eureka-server
 
When I run my application by first starting the eureka server, following by the client via 
 
mvn spring-boot:run 
 
The server successfully registers my client (I call it user-registration).
 
When I run my application through docker-compose, the client fails to register with the following output:
 
 DiscoveryClient_USER-REGISTRATION/0fd640cbc3ba:user-registration:9000: 
 registering service...
 user-registration_1  | 2017-06-21 04:36:05.120 ERROR 1 --- [nfoReplicator-0]        
 c.n.d.s.t.d.RedirectingEurekaHttpClient  : Request execution error
 user-registration_1  | 
 user-registration_1  | com.sun.jersey.api.client.ClientHandlerException: 
 java.net.ConnectException: Connection refused (Connection refused)
 
My first assumption was that running docker-compose ran into a race condition on waiting for the server to start, but my eureka client seems to have a heartbeat trying to call home to the server it's configured with. This means it's just not able to find the Eureka server I have registered (and is running, I can navigate to it on localhost:8671).
 
What am I missing here? Everything runs fine running locally with spring-boot starting up with it's own embedded tomcat containers. As soon as I start to do it with docker-compose, it doesn't want to work.
 
EDIT
 
I realized my problem, I believe. So docker doesn't run on localhost, it runs on the public IP it is assigned when I start up docker. Navigating to this ip + port shows my service running for Eureka Server. The client still doesn't register.
 
SO, I made changes to the application.yml file for my eureka client to:
 
serviceUrl:
  defaultZone: http://192.168.59.103:8761/eureka/
 
That IP is the one my docker daemon is running under. Now, it misses the first registration when I do docker-compose, but the second heartbeat picks up my client. 
 
How can I ensure the client waits until the server is FULLY up? I used the proper docker "links" field in my docket compose file, but it didn't work as I hoped. Additionally, how can I see the defaultZone file to be my DOCKER_HOST IP?
 
Final result
 
The resulting docker-compose file that got everything working for me was:
 
eureka-server:
  image: thorrism/eureka-server
  ports:
   - "8761:8761"
user-registration:
  image: thorrism/user-registration
  ports:
   - "9000:9000"
  links:
   - eureka-server
  environment:
    EUREKA_CLIENT_SERVICEURL_DEFAULTZONE: http://eureka-server:8761/eureka

原文：https://stackoverflow.com/questions/44667063