{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/22371","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/22371/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/22371/comments","events_url":"https://api.github.com/repos/docker/docker/issues/22371/events","html_url":"https://github.com/docker/docker/issues/22371","id":151457744,"number":22371,"title":"Xenial (16.04) - Failed to start Docker Application Container Engine","user":{"login":"Gbeschbacher","id":1677695,"avatar_url":"https://avatars.githubusercontent.com/u/1677695?v=3","gravatar_id":"","url":"https://api.github.com/users/Gbeschbacher","html_url":"https://github.com/Gbeschbacher","followers_url":"https://api.github.com/users/Gbeschbacher/followers","following_url":"https://api.github.com/users/Gbeschbacher/following{/other_user}","gists_url":"https://api.github.com/users/Gbeschbacher/gists{/gist_id}","starred_url":"https://api.github.com/users/Gbeschbacher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Gbeschbacher/subscriptions","organizations_url":"https://api.github.com/users/Gbeschbacher/orgs","repos_url":"https://api.github.com/users/Gbeschbacher/repos","events_url":"https://api.github.com/users/Gbeschbacher/events{/privacy}","received_events_url":"https://api.github.com/users/Gbeschbacher/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-04-27T18:29:22Z","updated_at":"2016-11-06T21:40:26Z","closed_at":"2016-04-28T16:28:31Z","body":"Even though i read all other issues reported already concerning docker support for xenial it still doesn't work for me. I cannot successfully install it neither via the suggested method on the official documentation nor with the fast-install via `wget` and `sudo dpkg`.\n\nFollowing i report some information i could find:\n\n```\n● docker.service - Docker Application Container Engine\n   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)\n   Active: failed (Result: exit-code) since Mit 2016-04-27 18:46:28 CEST; 7min ago\n     Docs: https://docs.docker.com\n  Process: 7537 ExecStart=/usr/bin/docker daemon -H fd:// (code=exited, status=1/FAILURE)\n Main PID: 7537 (code=exited, status=1/FAILURE)\n\nApr 27 18:46:27 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:27.366619877+02:00\" level=info msg=\"New containerd process, pid: 7552\\n\"\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.416215408+02:00\" level=error msg=\"devmapper: Unable to delete device: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-pool\"\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.416290179+02:00\" level=warning msg=\"devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.423610137+02:00\" level=error msg=\"[graphdriver] prior storage driver \\\"devicemapper\\\" failed: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.423644646+02:00\" level=fatal msg=\"Error starting daemon: error initializing graphdriver: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-pool\"\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28+02:00\" level=info msg=\"stopping containerd after receiving terminated\"\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: Failed to start Docker Application Container Engine.\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Unit entered failed state.\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Failed with result 'exit-code'.\n```\n\n```\nApr 27 18:46:26 gbeschbacher-xps sudo[7455]: pam_unix(sudo:session): session opened for user root by (uid=0)\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Reloading.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: apt-daily.timer: Adding 8h 56min 38.349166s random time.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Started ACPI event daemon.\n-- Subject: Unit acpid.service has finished start-up\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit acpid.service has finished starting up.\n-- \n-- The start-up result is done.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Started CUPS Scheduler.\n-- Subject: Unit cups.service has finished start-up\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit cups.service has finished starting up.\n-- \n-- The start-up result is done.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Reloading.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: apt-daily.timer: Adding 5h 49min 22.325636s random time.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Started ACPI event daemon.\n-- Subject: Unit acpid.service has finished start-up\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit acpid.service has finished starting up.\n-- \n-- The start-up result is done.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Started CUPS Scheduler.\n-- Subject: Unit cups.service has finished start-up\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit cups.service has finished starting up.\n-- \n-- The start-up result is done.\nApr 27 18:46:27 gbeschbacher-xps systemd[1]: Starting Docker Application Container Engine...\n-- Subject: Unit docker.service has begun start-up\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit docker.service has begun starting up.\nApr 27 18:46:27 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:27.366619877+02:00\" level=info msg=\"New containerd process, pid: 7552\\n\"\nApr 27 18:46:28 gbeschbacher-xps audit[7571]: AVC apparmor=\"STATUS\" operation=\"profile_replace\" name=\"docker-default\" pid=7571 comm=\"apparmor_parser\"\nApr 27 18:46:28 gbeschbacher-xps kernel: audit: type=1400 audit(1461775588.391:28): apparmor=\"STATUS\" operation=\"profile_replace\" name=\"docker-default\" pid=7571 comm=\"apparmor_parser\"\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.416215408+02:00\" level=error msg=\"devmapper: Unable to delete device: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-pool\"\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.416290179+02:00\" level=warning msg=\"devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.423610137+02:00\" level=error msg=\"[graphdriver] prior storage driver \\\"devicemapper\\\" failed: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28.423644646+02:00\" level=fatal msg=\"Error starting daemon: error initializing graphdriver: devicemapper: Can't set task name /dev/mapper/docker-259:2-5395073-pool\"\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE\nApr 27 18:46:28 gbeschbacher-xps docker[7537]: time=\"2016-04-27T18:46:28+02:00\" level=info msg=\"stopping containerd after receiving terminated\"\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: Failed to start Docker Application Container Engine.\n-- Subject: Unit docker.service has failed\n-- Defined-By: systemd\n-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel\n-- \n-- Unit docker.service has failed.\n-- \n-- The result is failed.\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Unit entered failed state.\nApr 27 18:46:28 gbeschbacher-xps systemd[1]: docker.service: Failed with result 'exit-code'.\nApr 27 18:46:30 gbeschbacher-xps sudo[7455]: pam_unix(sudo:session): session closed for user root\nApr 27 18:48:19 gbeschbacher-xps pkexec[7655]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)\nApr 27 18:48:19 gbeschbacher-xps pkexec[7655]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session\nApr 27 18:48:19 gbeschbacher-xps pkexec[7655]: gbeschbacher: Executing command [USER=root] [TTY=unknown] [CWD=/home/gbeschbacher] [COMMAND=/usr/lib/update-notifier/package-system-locked]\nApr 27 19:00:10 gbeschbacher-xps upowerd[1114]: (upowerd:1114): UPower-Linux-WARNING **: energy 57,532000 bigger than full 53,405200\nApr 27 19:00:10 gbeschbacher-xps kernel: ACPI Error: Cannot release Mutex [PATM], not acquired (20160108/exmutex-393)\nApr 27 19:00:10 gbeschbacher-xps kernel: ACPI Error: Method parse/execution failed [\\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff8802780e88c0), AE_AML_MUTEX_NOT_ACQUIRED (20160108/psparse-542)\n```\n\n```\n~ ❯❯❯ uname -a\nLinux xenial 4.6.0-999-generic #201603262200 SMP Sun Mar 27 02:02:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux\n```\n\nI appreciate any information on this case and am willing to try out everything possible to get this to work :)\nThanks in advance,\nGeorg\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/258712905","html_url":"https://github.com/docker/docker/issues/22371#issuecomment-258712905","issue_url":"https://api.github.com/repos/docker/docker/issues/22371","id":258712905,"user":{"login":"arno01","id":3791945,"avatar_url":"https://avatars.githubusercontent.com/u/3791945?v=3","gravatar_id":"","url":"https://api.github.com/users/arno01","html_url":"https://github.com/arno01","followers_url":"https://api.github.com/users/arno01/followers","following_url":"https://api.github.com/users/arno01/following{/other_user}","gists_url":"https://api.github.com/users/arno01/gists{/gist_id}","starred_url":"https://api.github.com/users/arno01/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arno01/subscriptions","organizations_url":"https://api.github.com/users/arno01/orgs","repos_url":"https://api.github.com/users/arno01/repos","events_url":"https://api.github.com/users/arno01/events{/privacy}","received_events_url":"https://api.github.com/users/arno01/received_events","type":"User","site_admin":false},"created_at":"2016-11-06T21:40:26Z","updated_at":"2016-11-06T21:40:26Z","body":"Maybe this will help someone too.\r\nI've got a 4.5.7 kernel and Ubuntu Xenial (16.04)\r\n\r\n\r\n1) The Docker installation process hang:\r\n\r\n```\r\nroot@scw-73792f:~# apt -y install docker-engine\r\n...\r\nSetting up aufs-tools (1:3.2+20130722-1.1ubuntu1) ...\r\nSetting up cgroupfs-mount (1.2) ...\r\nSetting up libltdl7:amd64 (2.4.6-0.1) ...\r\nSetting up docker-engine (1.12.3-0~xenial) ...\r\nProgress: [ 89%]\r\n```\r\n\r\n**Process backtrace**\r\n```\r\nroot     19943 19942  0 20:30 pts/1    00:00:00 /bin/systemd-tty-ask-password-agent --watch\r\nroot     19942 19908  0 20:30 pts/1    00:00:00 systemctl start docker.service\r\nroot     19908 19855  0 20:30 pts/1    00:00:00 /bin/sh /usr/sbin/invoke-rc.d docker start\r\nroot     19855 19740  0 20:30 pts/1    00:00:00 /bin/sh /var/lib/dpkg/info/docker-engine.postinst configure\r\nroot     19740 18060  0 20:30 pts/1    00:00:00 /usr/bin/dpkg --status-fd 24 --configure busybox-initramfs:amd64 cpio:amd64 initramfs-tools-bin:amd64 libklibc:amd64 klibc-utils:amd64 initramfs-tools-core:all linux-base:all initramfs-tools:all libapparmor-perl:amd64 apparmor:amd64 aufs-tools:amd64 cgroupfs-mount:all libltdl7:amd64 docker-engine:amd64 liberror-perl:all git-man:all git:amd64 patch:amd64\r\nroot     18060  4323  0 20:29 pts/0    00:00:01 apt -y install docker-engine\r\n```\r\n\r\nI have noticed the dockerd process was also running at that time:\r\n```\r\n             ├─docker.service\r\n             │ ├─19945 /usr/bin/dockerd -H fd://\r\n             │ └─19966 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime docker-runc\r\n```\r\n\r\nBut `docker info` commands were hanging too.\r\n\r\nI have tried restarting docker service, which caused the installation to fail with the following output:\r\n```\r\napt -y install docker-engine (from above)\r\n...\r\nProcessing triggers for systemd (229-4ubuntu12) ...\r\nProcessing triggers for libc-bin (2.23-0ubuntu4) ...\r\nErrors were encountered while processing:\r\n docker-engine\r\nE: Sub-process /usr/bin/dpkg returned an error code (1)\r\nroot@scw-73792f:~# echo $?\r\n100\r\n```\r\n\r\nThen, each time I have been trying to continue the installation `apt -f install`, I was getting the same error. And each time I was trying to restart docker service manually, the following message was getting into `/var/log/syslog` file:\r\n\r\n```\r\n...\r\nNov  6 21:16:30 scw-73792f dockerd[20892]: time=\"2016-11-06T21:16:30.251654378Z\" level=error msg=\"[graphdriver] prior storage driver \\\"devicemapper\\\" failed: devicemapper: Can't set task name /dev/mapper/docker-43:0-395135-pool\"\r\n...\r\n```\r\n\r\nSo it made me thinking that something gone wrong with he devicemapper. Actually I could not remove the docker devicemapper loop devices using the `losetup -D`:\r\n```\r\nroot@scw-73792f:~# losetup -a\r\n/dev/loop0: [11008]:395139 (/var/lib/docker/devicemapper/devicemapper/data)\r\n/dev/loop1: [11008]:395140 (/var/lib/docker/devicemapper/devicemapper/metadata)\r\nroot@scw-73792f:~# losetup -D\r\nroot@scw-73792f:~# losetup -a\r\n/dev/loop0: [11008]:395139 (/var/lib/docker/devicemapper/devicemapper/data)\r\n/dev/loop1: [11008]:395140 (/var/lib/docker/devicemapper/devicemapper/metadata)\r\n```\r\n\r\nThe only thing that helped is `dmsetup`:\r\n```\r\nroot@scw-73792f:~# dmsetup table\r\ndocker-43:0-395135-pool: 0 209715200 thin-pool 7:1 7:0 128 32768 1 skip_block_zeroing \r\nroot@scw-73792f:~# dmsetup remove docker-43:0-395135-pool\r\nroot@scw-73792f:~# dmsetup table\r\nNo devices found\r\nroot@scw-73792f:~# losetup -a\r\nroot@scw-73792f:~# \r\n```\r\n\r\nThen the installation could successfully be finished:\r\n```\r\nroot@scw-73792f:~# apt -f install\r\nReading package lists... Done\r\nBuilding dependency tree       \r\nReading state information... Done\r\n0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.\r\n1 not fully installed or removed.\r\nAfter this operation, 0 B of additional disk space will be used.\r\nSetting up docker-engine (1.12.3-0~xenial) ...\r\nroot@scw-73792f:~# echo $?\r\n0\r\n```\r\n\r\nVoila!\r\n\r\nI need to mention, that on the moment of Docker installation, I did not have `dmsetup` installed at all.\r\nSo I think that is the real cause of the problem.\r\n\r\nActually, without having `dmsetup` installed, neither `cryptsetup luksOpen` was working for me. Since it was hanging on `semop(0, [{0, 0, 0}], 1)` syscall due to missing udev rules `/lib/udev/rules.d/55-dm.rules`.\r\n\r\nI think this was due to missing hooks which dmsetup is bringing with itself:\r\n```\r\nroot@scw-73792f:~# dpkg -L dmsetup\r\n...\r\n/lib/udev/rules.d/55-dm.rules\r\n/lib/udev/rules.d/60-persistent-storage-dm.rules\r\n...\r\n```\r\n\r\nSo maybe it would be making sense to add the dmsetup as a dependency in docker-engine .deb, what do you think, @thaJeztah ?\r\n"}}
{"actor":{"display_login":"arno01"}}