** Also affects: docker.io (Ubuntu Vivid) Importance: Undecided Status: New
** Also affects: docker.io (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: docker.io (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: docker.io (Ubuntu Vivid) Importance: Undecided => High ** Changed in: docker.io (Ubuntu Trusty) Importance: Undecided => High ** Changed in: docker.io (Ubuntu Utopic) Importance: Undecided => High ** Changed in: docker.io (Ubuntu Vivid) Status: New => In Progress ** Changed in: docker.io (Ubuntu Utopic) Status: New => In Progress ** Changed in: docker.io (Ubuntu Trusty) Status: New => In Progress ** Description changed: - Whilst testing security updates for bug 1396572, I noticed that after - restarting docker, existing containers where no longer running and I was - unable to restart them: + Impact: + Docker users are unable to upgrade packaging or restart the docker service without cleaning up stale mounts first; impacted containers will not start post restart of the docker daemon. + + Test case: + NOTE: this must be done on a ext4 filesystem - btrfs users are not impacted. + <create a docker image> + docker run -d <uuid of image> + sudo service docker stop + sudo service docker start + docker ps -a + docker start <uuid of container> + container will fails to start as in original bug report. + + Regression potential: + Minimal - the init script and upstart configuration will attempt cleanup of stale mounts in pre-start. + + Original bug report: + Whilst testing security updates for bug 1396572, I noticed that after restarting docker, existing containers where no longer running and I was unable to restart them: ubuntu@juju-jp-machine-24:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES - dd470c1d3430 38e88eeb106a memcached /bin/bash About an hour ago Exited (0) About a minute ago stupefied_newton - ubuntu@juju-jp-machine-24:~$ docker start stupefied_newton + dd470c1d3430 38e88eeb106a memcached /bin/bash About an hour ago Exited (0) About a minute ago stupefied_newton + ubuntu@juju-jp-machine-24:~$ docker start stupefied_newton Error response from daemon: Cannot start container stupefied_newton: Error getting container dd470c1d3430b651bca3ca3b7f35235529f5eaf7db03a460157d646655fbe020 from driver devicemapper: Error mounting '/dev/mapper/docker-253:1-131799-dd470c1d3430b651bca3ca3b7f35235529f5eaf7db03a460157d646655fbe020' on '/var/lib/docker/devicemapper/mnt/dd470c1d3430b651bca3ca3b7f35235529f5eaf7db03a460157d646655fbe020': device or resource busy 2014/12/19 16:13:18 Error: failed to start one or more containers This appears to be related to https://github.com/docker/docker/issues/5684 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: docker.io 1.0.1~dfsg1-0ubuntu1~ubuntu0.14.04.1 ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Fri Dec 19 16:13:00 2014 Ec2AMI: ami-0000002c Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-00000002 Ec2Ramdisk: ari-00000002 SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404300 Title: After restarting docker daemon, unable to restart existing containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1404300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs