Spring Cloud Netflix和Docker Compose-无法在eureka注册服务

Question

我正在尝试使用docker-compose在本地（Ubuntu）运行两个简单的服务：一个eureka服务器和一个config服务器（它也是一个eureka客户机）。这两个文件都有简单的dockerfiles，运行java-jar，公开它们的端口，并且单独运行良好。我还尝试添加eureka.client.service-url.defaultzone=http://company-service-discovery:8761/eureka来查看它是否会注册自己，结果成功了。

我的配置服务器无法成功注册到eureka服务器，我搜索了它，但没有看到任何帮助我解决这个问题的东西。

通过以下示例，Web应该能够使用postgres:/db:5432与数据库通信。

version: "3"
services:
  web:
    build: .
    ports:
      - "8000:8000"
  db:
    image: postgres
    ports:
      - "8001:5432"

我使用了相同的方法来配置我的服务，但是我的配置服务器在尝试注册时连接被拒绝：

version: '3.3'
services:
  company-service-discovery:
    build: company-service-discovery/
    ports:
      - "8761:8761"
  company-config-server:
    build: company-config-server/
    ports:
      - "8888:8888"
    links:
      - company-service-discovery

server:
  port: 8888

management:
  security:
    enabled: false

spring:
  application:
    name: company-config-server
  cloud:
    config:
      server:
        native:
          search-locations: classpath:/shared
  profiles:
    include: native

eureka:
  client:
    service-url:
      defaultZone: http://company-service-discovery:8761/eureka

spring:
  application:
    name: company-service-discovery

server:
  port: 8761

management:
  security:
    enabled: false

2017-07-26 14:25:05.738  WARN 1 --- [nfoReplicator-0] c.n.d.s.t.d.RetryableEurekaHttpClient    : Request execution failed with message: java.net.ConnectException: Connection refused (Connection refused)
2017-07-26 14:25:05.739  WARN 1 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_COMPANY-CONFIG-SERVER/365d20275ab0:company-config-server:8888 - registration failed Cannot execute request on any known server

我的配置有什么问题吗？我怎么才能让它工作呢？

Answer 1

将defaultzone配置也添加到Eureka服务器的属性中（并将配置服务器bootstrap.yml中的service-url更改为serviceURL)。

spring:
  application:
    name: company-service-discovery

eureka:
  client:
    serviceUrl:
      defaultZone: http://company-service-discovery:8761/eureka

server:
  port: 8761

management:
  security:
    enabled: false