| 2014-12-19 16:16:44 |
James Page |
bug |
|
|
added bug |
| 2015-01-22 08:51:07 |
James Page |
nominated for series |
|
Ubuntu Vivid |
|
| 2015-01-22 08:51:07 |
James Page |
bug task added |
|
docker.io (Ubuntu Vivid) |
|
| 2015-01-22 08:51:07 |
James Page |
nominated for series |
|
Ubuntu Utopic |
|
| 2015-01-22 08:51:07 |
James Page |
bug task added |
|
docker.io (Ubuntu Utopic) |
|
| 2015-01-22 08:51:07 |
James Page |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-01-22 08:51:07 |
James Page |
bug task added |
|
docker.io (Ubuntu Trusty) |
|
| 2015-01-22 08:51:26 |
James Page |
docker.io (Ubuntu Vivid): importance |
Undecided |
High |
|
| 2015-01-22 08:51:29 |
James Page |
docker.io (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2015-01-22 08:51:32 |
James Page |
docker.io (Ubuntu Utopic): importance |
Undecided |
High |
|
| 2015-01-22 08:51:35 |
James Page |
docker.io (Ubuntu Vivid): status |
New |
In Progress |
|
| 2015-01-22 08:51:38 |
James Page |
docker.io (Ubuntu Utopic): status |
New |
In Progress |
|
| 2015-01-22 08:51:40 |
James Page |
docker.io (Ubuntu Trusty): status |
New |
In Progress |
|
| 2015-01-22 08:54:00 |
James Page |
description |
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
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) |
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
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) |
|
| 2015-01-22 09:17:41 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/vivid-proposed/docker.io |
|
| 2015-01-22 09:36:50 |
Launchpad Janitor |
docker.io (Ubuntu Vivid): status |
In Progress |
Fix Released |
|
| 2015-01-22 09:47:34 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/docker.io |
|
| 2015-10-28 18:25:38 |
Launchpad Janitor |
docker.io (Ubuntu Trusty): status |
In Progress |
Fix Released |
|
| 2016-04-24 10:42:49 |
Rolf Leggewie |
docker.io (Ubuntu Utopic): status |
In Progress |
Won't Fix |
|
