docker-compose up错误，地址无效

Question

我想使用Elastic的docker-elk，然后克隆了elastic github代码。我想为每个容器使用一个特定的IP，所以我为每个容器定义一个特定的IP，当我运行时docker-compose up，遇到错误

ERROR: for elasticsearch  Cannot start service elasticsearch: Invalid address 172.18.1.3: It does not belong to any of this network's subnets
ERROR: Encountered errors while bringing up the project.

它不显示任何网络的子网，但是我定义了子网，docker-compose.yml就像这样

version: '2'

services:

  elasticsearch:
    build: elasticsearch/      
    ports:
      - "9200:9200"
      - "9300:9300"
    environment:
      ES_JAVA_OPTS: "-Xmx256m -Xms256m"
    networks:
      elk:
        ipv4_address: 172.18.1.3

  logstash:
    build: logstash/
    ports:
      - "5000:5000"
    environment:
      LS_JAVA_OPTS: "-Xmx256m -Xms256m"
    networks:
      elk:
        ipv4_address: 172.18.1.4
    depends_on:
      - elasticsearch

  kibana:
    build: kibana/
    ports:
      - "5601:5601"
    networks:
      elk:
        ipv4_address: 172.18.1.5
    depends_on:
      - elasticsearch

networks:

  elk:
    driver: bridge
    ipam:
      config:
        - subnet: 172.18.1.0/24

和 docker version

Client:
 Version:      17.06.0-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:20:36 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:21:56 2017
 OS/Arch:      linux/amd64
 Experimental: false

Answer 1

使用docker-compose down并尝试运行docker-compose up。这对我有用

Answer 2

我刚遇到这个问题，而我的问题似乎是docker如何缓存网络和容器的问题。我必须使用docker network rm先前创建的网络。我也不得不docker ps -a和docker rm他们正在缓存的使用网络，你会被删除以前创建的容器。删除所有剩余的工件后，它可以正确启动。

Answer 3

根据 Compose文档，该ipam块必须定义子网范围和网关。所以只需将您的更新为：

ipam:
  config:        
    - driver: default
      subnet: 172.18.1.0/24
      gateway: 172.18.1.1