Question

我一直在尝试在Ubuntu 16.04 上使用 Docker（1.10），但安装失败，因为 Docker Service无法启动。我已经尝试通过 docker.io ， docker-engine apt软件包和curl -sSL https://get.docker.com/ | sh安装docker但它不起作用。< / p>

我的主机信息是：

Linux Xenial 4.5.3-040503-generic #201605041831 SMP Wed May 4 22:33:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

这是 systemctl status docker.service ：

● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since sáb 2016-05-14 15:17:31 CEST; 12min ago Docs: https://docs.docker.com Process: 22479 ExecStart=/usr/bin/docker daemon -H fd:// (code=exited, status=1/FAILURE) Main PID: 22479 (code=exited, status=1/FAILURE) may 14 15:17:30 Xenial docker[22479]: time="2016-05-14T15:17:30.103601523+02:00" level=info msg="New containerd process, pid: 22485\n" may 14 15:17:31 Xenial docker[22479]: time="2016-05-14T15:17:31.149064723+02:00" level=error msg="devmapper: Unable to delete device: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool" may 14 15:17:31 Xenial docker[22479]: time="2016-05-14T15:17:31.149127439+02:00" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section." may 14 15:17:31 Xenial docker[22479]: time="2016-05-14T15:17:31.153010028+02:00" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool" may 14 15:17:31 Xenial docker[22479]: time="2016-05-14T15:17:31.153130839+02:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool" may 14 15:17:31 Xenial systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE may 14 15:17:31 Xenial docker[22479]: time="2016-05-14T15:17:31+02:00" level=info msg="stopping containerd after receiving terminated" may 14 15:17:31 Xenial systemd[1]: Failed to start Docker Application Container Engine. may 14 15:17:31 Xenial systemd[1]: docker.service: Unit entered failed state. may 14 15:17:31 Xenial systemd[1]: docker.service: Failed with result 'exit-code'.

这是 sudo docker daemon -D

DEBU[0000] docker group found. gid: 999 DEBU[0000] Listener created for HTTP on unix (/var/run/docker.sock) INFO[0000] previous instance of containerd still alive (23050) DEBU[0000] containerd connection state change: CONNECTING DEBU[0000] Using default logging driver json-file DEBU[0000] Golang's threads limit set to 55980 DEBU[0000] received past containerd event: &types.Event{Type:"live", Id:"", Status:0x0, Pid:"", Timestamp:0x57372cae} DEBU[0000] containerd connection state change: READY DEBU[0000] devicemapper: driver version is 4.34.0 DEBU[0000] devmapper: Generated prefix: docker-8:6-2101297 DEBU[0000] devmapper: Checking for existence of the pool docker-8:6-2101297-pool DEBU[0000] devmapper: poolDataMajMin=7:0 poolMetaMajMin=7:1 DEBU[0000] devmapper: Major:Minor for device: /dev/loop0 is:7:0 DEBU[0000] devmapper: Major:Minor for device: /dev/loop1 is:7:1 DEBU[0000] devmapper: loadDeviceFilesOnStart() DEBU[0000] devmapper: Skipping file /var/lib/docker/devicemapper/metadata/transaction-metadata DEBU[0000] devmapper: loadDeviceFilesOnStart() END DEBU[0000] devmapper: constructDeviceIDMap() DEBU[0000] devmapper: constructDeviceIDMap() END DEBU[0000] devmapper: Rolling back open transaction: TransactionID=1 hash= device_id=1 ERRO[0000] devmapper: Unable to delete device: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool WARN[0000] devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section. DEBU[0000] devmapper: Initializing base device-mapper thin volume DEBU[0000] devicemapper: CreateDevice(poolName=/dev/mapper/docker-8:6-2101297-pool, deviceID=1) DEBU[0000] devmapper: Error creating device: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool DEBU[0000] devmapper: Error device setupBaseImage: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool ERRO[0000] [graphdriver] prior storage driver "devicemapper" failed: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool DEBU[0000] Cleaning up old mountid : start. FATA[0000] Error starting daemon: error initializing graphdriver: devicemapper: Can't set task name /dev/mapper/docker-8:6-2101297-pool

这是 ./check-config.sh 输出：

warning: /proc/config.gz does not exist, searching other paths for kernel config ... info: reading kernel config from /boot/config-4.5.3-040503-generic ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - apparmor: enabled and tools installed - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_MACVLAN: enabled (as module) - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled (as module) - CONFIG_BRIDGE_NETFILTER: enabled (as module) - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_KMEM: missing - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: missing (note that cgroup swap accounting is not enabled in your kernel config, you can enable it by setting boot option "swapaccount=1") - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: enabled - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: missing - CONFIG_EXT3_FS: missing - CONFIG_EXT3_FS_XATTR: missing - CONFIG_EXT3_FS_POSIX_ACL: missing - CONFIG_EXT3_FS_SECURITY: missing (enable these ext3 configs if you are using ext3 as backing filesystem) - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled (as module) - "devicemapper": - CONFIG_BLK_DEV_DM: enabled - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled (as module) - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing

如果有人能帮助我，我会非常感激

Answer 1

我遇到了同样的问题，我尝试用Salva Cort的建议修复它，但打印/etc/default/docker说：

＃此文件不适用于SYSTEMD

所以这是一个永久修复that works for systemd（Ubuntu 15.04及更高版本）：

使用以下内容创建新文件/etc/systemd/system/docker.service.d/overlay.conf：
```
[Service]
ExecStart=
ExecStart=/usr/bin/docker daemon -H fd:// -s overlay
```
执行以下命令刷新更改：
```
sudo systemctl daemon-reload
```

验证配置是否已加载：

systemctl show --property=ExecStart docker

重启docker：
```
sudo systemctl restart docker
```

Answer 2

以下取消屏蔽命令对我有用（Ubuntu 18）。希望它可以帮助某人... :-)

sudo systemctl unmask docker.service
sudo systemctl unmask docker.socket
sudo systemctl start docker.service

Answer 3

升级码头工具从17.05-ce到17.06-ce后通过docker-machine我遇到了同样的问题

更新/etc/systemd/system/docker.service.d/10-machine.conf

替换

`docker daemon` => `dockerd`

示例来自

[Service]
ExecStart=
ExecStart=/usr/bin/docker deamon -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=generic
Environment=

到

[Service]
ExecStart=
ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2376 -H unix:///var/run/docker.sock --storage-driver aufs --tlsverify --tlscacert /etc/docker/ca.pem --tlscert /etc/docker/server.pem --tlskey /etc/docker/server-key.pem --label provider=generic
Environment=

执行以下命令刷新更改：
```
sudo systemctl daemon-reload
```
重启docker：
```
sudo systemctl restart docker
```

Answer 4

好吧，最后我修好了

您需要做的就是在我的案例中加载其他 storage-driver ，我将使用 overlay ：

停用Docker服务：sudo systemctl stop docker.service
启动Docker守护程序（overlay驱动程序）：sudo docker daemon -s overlay
运行演示容器：sudo docker run hello-world

要永久更改这些更改，您必须修改 /etc/default/docker 文件并添加选项：

DOCKER_OPTS="-s overlay"

下次加载 Docker服务时，它会运行docker daemon -s overlay

Answer 5

按照本博客中的说明，我已经能够在内核升级后使其正常工作。

https://mymemorysucks.wordpress.com/2016/03/31/docker-graphdriver-and-aufs-failed-driver-not-supported-error-after-ubuntu-upgrade/

sudo apt-get update
sudo apt-get install linux-image-extra-$(uname -r) linux-image-extra-virtual

sudo modprobe aufs

sudo service docker restart

Answer 6

在查看其他一些答案之后，问题似乎是服务没有使用-s overlay选项运行。

我也碰巧注意到docker试图在通话结束时启动${DOCKER_OPTS}。

我能够export DOCKER_OPTS="-s overlay"（默认情况下，bc为空，DOCKER_OPTS为空）并让docker运行。

Answer 7

至于我，我收到了这个错误。

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

最后，我发现/etc/docker/daemon.json错误，因为我添加了registry-mirrors

{
    "runtimes": {

        "nvidia": {
            "path": "/usr/bin/nvidia-container-runtime",
            "runtimeArgs": []
        }
    }    

    # I forget to add a comma , here !!!!!!!
    "registry-mirrors": ["https://docker.mirrors.ustc.edu.cn"]
}

在我添加它之后，systemctl restart docker，我解决了它。

Answer 8

就我而言，我从journalctl -xe command收到以下错误消息

unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character 'â' looking for beginning of object key string

只需使用

清洁/etc/docker/daemon.json

{
}

Answer 9

今天，升级到ubuntu内核后遇到了这个问题，并尝试了上述多种解决方案。但是，唯一可行的方法（Ubuntu 16.04.6 LTS）是删除（或重命名）文件夹：/ var / lib / docker

请注意，此将删除所有docker映像，容器和卷等。因此，在应用或进行备份之前了解其含义！

这里有更多详细信息： https://github.com/docker/for-linux/issues/162

Answer 10

在Ubuntu 18.04.3 LTS上的新Docker安装（版本19.03.3-rc1）上，我遇到了类似的问题。默认情况下，新安装中不存在 /etc/docker/daemon.json 文件。在学习完教程之后，我通过创建一个新的 daemon.json 文件将存储驱动程序更改为 devicemapper 。它可以正常工作，但是后来我删除了daemon.json文件，以为它会还原为默认值，但是那不起作用，并且服务也无法启动。

使用默认的存储驱动程序重新创建 /etc/docker/daemon.json 文件。

{
    "storage-driver": "overlay2"
}

Answer 11

sudo dockerd --debug 将有助于解决实际痛点我在 ubuntu 20 LTS 上使用它修复了相同的错误

无法在Ubuntu 16.04中启动Docker Service

11 个答案: