EC2实例重启时如何自动重启docker compose集群

我有一个docker-compose.yml文件：

version: '2.2'
services:
  kibana:
    restart: always
    depends_on:
      - es01
      - es02
    image: docker.elastic.co/kibana/kibana:7.3.1
    container_name: kibana
    ports:
      - 5601:5601
    environment:
      ELASTICSEARCH_HOSTS: http://es01:9200
      ELASTICSEARCH_URL: http://es01:9200
  es01:
    restart: always
    image: docker.elastic.co/elasticsearch/elasticsearch:7.3.1
    container_name: es01
    environment:
      - node.name=es01
      - discovery.seed_hosts=es02
      - cluster.initial_master_nodes=es01,es02
      - cluster.name=docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - esdata01:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
      - 9300:9300
  es02:
    restart: always
    image: docker.elastic.co/elasticsearch/elasticsearch:7.3.1
    container_name: es02
    environment:
      - node.name=es02
      - discovery.seed_hosts=es01
      - cluster.initial_master_nodes=es01,es02
      - cluster.name=docker-cluster
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - esdata02:/usr/share/elasticsearch/data

volumes:
  esdata01:
    driver: local
  esdata02:
    driver: local

但是当ec2实例重新启动时，这些容器没有重新启动。也许我应该用这样的方式来代替：

docker-compose up -d --restart   # the --restart flag maybe?

?

注意yml文件中的“restart”属性，猜测它们在这种情况下没有做任何事情

但没有--restart标志：

docker compose up-d--重新启动 为服务构建（重新）创建、启动和附加到容器

Unless they are already running, this command also starts any linked services.

The `docker-compose up` command aggregates the output of each container. When
the command exits, all containers are stopped. Running `docker-compose up -d`
starts the containers in the background and leaves them running.

If there are existing containers for a service, and the service's configuration
or image was changed after the container's creation, `docker-compose up` picks
up the changes by stopping and recreating the containers (preserving mounted
volumes). To prevent Compose from picking up changes, use the `--no-recreate`
flag.

If you want to force Compose to stop and recreate all containers, use the
`--force-recreate` flag.

Usage: up [options] [--scale SERVICE=NUM...] [SERVICE...]

Options:
    -d, --detach               Detached mode: Run containers in the background,
                               print new container names. Incompatible with
                               --abort-on-container-exit.
    --no-color                 Produce monochrome output.
    --quiet-pull               Pull without printing progress information
    --no-deps                  Don't start linked services.
    --force-recreate           Recreate containers even if their configuration
                               and image haven't changed.
    --always-recreate-deps     Recreate dependent containers.
                               Incompatible with --no-recreate.
    --no-recreate              If containers already exist, don't recreate
                               them. Incompatible with --force-recreate and -V.
    --no-build                 Don't build an image, even if it's missing.
    --no-start                 Don't start the services after creating them.
    --build                    Build images before starting containers.
    --abort-on-container-exit  Stops all containers if any container was
                               stopped. Incompatible with -d.
    -t, --timeout TIMEOUT      Use this timeout in seconds for container
                               shutdown when attached or when containers are
                               already running. (default: 10)
    -V, --renew-anon-volumes   Recreate anonymous volumes instead of retrieving
                               data from the previous containers.
    --remove-orphans           Remove containers for services not defined
                               in the Compose file.
    --exit-code-from SERVICE   Return the exit code of the selected service
                               container. Implies --abort-on-container-exit.
    --scale SERVICE=NUM        Scale SERVICE to NUM instances. Overrides the
                               `scale` setting in the Compose file if present.

我正在寻找与之相当的：

docker run -d -p 27017:27017 \
    --restart unless-stopped \    # RESTART
    --name 'interos-mongo' \
    'mongo:4.0' 

---

实际上，

docker compose

不处理真正的重启，这些重启是由

dockerd

完成的

撰写配置文件中写入的重新启动策略最终将写入容器的重新启动策略，您可以使用以下命令进行检查

docker inspect --format '{{.HostConfig.RestartPolicy}}' you-container-ID-or-name

回到您的问题，您是否已将dockerd设置为自动启动？i、 e.

systemctl启用docker

---

外部参照：

事实上，

docker compose

不处理真正的重启，这些重启是由

dockerd

完成的

撰写配置文件中写入的重新启动策略最终将写入容器的重新启动策略，您可以使用以下命令进行检查

docker inspect --format '{{.HostConfig.RestartPolicy}}' you-container-ID-or-name

回到您的问题，您是否已将dockerd设置为自动启动？i、 e.

systemctl启用docker

外部参照：