After restarting docker daemon, unable to restart existing containers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Utopic |
Won't Fix
|
High
|
Unassigned | ||
Vivid |
Fix Released
|
High
|
Unassigned |
Bug Description
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@
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@
Error response from daemon: Cannot start container stupefied_newton: Error getting container dd470c1d3430b65
2014/12/19 16:13:18 Error: failed to start one or more containers
This appears to be related to https:/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: docker.io 1.0.1~dfsg1-
ProcVersionSign
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
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)
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: | updated |
Bug raised against trusty version; however I see this issue in 14.10 and vivid development as well.