docker 容器不会随 docker swarm 自动启动答案

【问题标题】：docker containers don't start automatically with docker swarmdocker 容器不会随 docker swarm 自动启动
【发布时间】：2017-08-29 19:44:11
【问题描述】：

我的系统昨天就这样崩溃了，我无法恢复它。我没有设置这个，所以我不知道所有的细节，但请询问任何需要的细节。过去，在任何 VM 重新启动时，系统都会自动开始工作，但在这次崩溃之后，它就不再工作了：

这是我的docker info 输出

Containers: 168
 Running: 0
 Paused: 0
 Stopped: 168
Images: 241
Server Version: 1.12.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1228
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay bridge host null
Swarm: pending
 NodeID: bg8sh8m6zm5llezlmcw00nqx6
 Is Manager: true
 ClusterID: 1wfvx3ze7tm1bb56a5zyk9xqs
 Managers: 1
 Nodes: 2
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: ADDRESS //hidden for security reasons
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-91-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 6.804 GiB
Name: swarm-manager-1
ID: AXPO:VFSV:TDT3:6X7Y:QNAO:OZJN:U23R:V5S2:FU33:WUNI:CRPK:2E2C
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 127.0.0.0/8

我的 docker 节点 ls 输出：

ID                           HOSTNAME         STATUS   AVAILABILITY  MANAGER STATUS
bg8sh8m6zm5llezlmcw00nqx6 *  swarm-manager-1  Ready    Active        Leader
c21j8nzzy3151vv06m54yyd1u    swarm-worker-1   Unknown  Active

这是来自 docker node inspect swarm-manager-1的输出

[
    {
        "ID": "bg8sh8m6zm5llezlmcw00nqx6",
        "Version": {
            "Index": 67823
        },
        "CreatedAt": "2016-10-13T23:46:00.580142516Z",
        "UpdatedAt": "2017-08-29T19:48:35.4197366Z",
        "Spec": {
            "Role": "manager",
            "Availability": "active"
        },
        "Description": {
            "Hostname": "swarm-manager-1",
            "Platform": {
                "Architecture": "x86_64",
                "OS": "linux"
            },
            "Resources": {
                "NanoCPUs": 2000000000,
                "MemoryBytes": 7305609216
            },
            "Engine": {
                "EngineVersion": "1.12.2",
                "Plugins": [
                    {
                        "Type": "Network",
                        "Name": "bridge"
                    },
                    {
                        "Type": "Network",
                        "Name": "host"
                    },
                    {
                        "Type": "Network",
                        "Name": "null"
                    },
                    {
                        "Type": "Network",
                        "Name": "overlay"
                    },
                    {
                        "Type": "Volume",
                        "Name": "local"
                    }
                ]
            }
        },
        "Status": {
            "State": "ready"
        },
        "ManagerStatus": {
            "Leader": true,
            "Reachability": "reachable",
            "Addr": "ADDRESS" //hidden
        }
    }
]

这是docker node inspect swarm-worker-1的输出

[
    {
        "ID": "c21j8nzzy3151vv06m54yyd1u",
        "Version": {
            "Index": 67824
        },
        "CreatedAt": "2017-02-21T05:42:31.467777741Z",
        "UpdatedAt": "2017-08-29T19:48:35.4252027Z",
        "Spec": {
            "Role": "worker",
            "Availability": "active"
        },
        "Description": {
            "Hostname": "swarm-worker-1",
            "Platform": {
                "Architecture": "x86_64",
                "OS": "linux"
            },
            "Resources": {
                "NanoCPUs": 2000000000,
                "MemoryBytes": 7305609216
            },
            "Engine": {
                "EngineVersion": "1.12.2",
                "Plugins": [
                    {
                        "Type": "Network",
                        "Name": "bridge"
                    },
                    {
                        "Type": "Network",
                        "Name": "host"
                    },
                    {
                        "Type": "Network",
                        "Name": "null"
                    },
                    {
                        "Type": "Network",
                        "Name": "overlay"
                    },
                    {
                        "Type": "Volume",
                        "Name": "local"
                    }
                ]
            }
        },
        "Status": {
            "State": "unknown",
            "Message": "Node moved to \"unknown\" state due to leadership change in cluster"
        }
    }
]

任何想法如何让它恢复工作？

【问题讨论】：

您是否在您的堆栈中尝试过autorestart？，看看这个文档docs.docker.com/docker-cloud/apps/autorestart/…
@juliansalas 我没有使用 docker-cloud。但问题是它工作得很好，所以我想已经有一些重启机制......
在 swarm worker 上执行 docker swarm leave，然后在 master 上运行 docker swarm join-token worker 并在 worker 上执行生成的令牌命令。它应该开始工作。崩溃可能导致了问题。如果这没有帮助，请告诉我们
@TarunLalwani 谢谢。让它工作（Y）

标签： docker virtual-machine containers docker-swarm

【解决方案1】：

在 swarm worker 上执行 docker swarm leave，然后在 master 上 run docker swarm join-token worker 并在 worker 上执行生成的令牌命令。它应该开始工作。

崩溃可能导致了问题。这会破坏 swarm 的状态，因此您需要重新创建它

【讨论】：