-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Closed
Labels
exp/expertkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
Description
When this occurs it renders the child container unusable unless one commits the container's image and runs a new container from it without -volumes-from.
$ docker run -v /mnt/vol -name data_container busybox touch /mnt/vol/base
$ docker run -name child -i -volumes-from data_container ubuntu ls -al /mnt{/vol,}
/mnt:
total 12
drwxr-xr-x 3 root root 4096 Jan 16 21:54 .
drwxr-xr-x 29 root root 4096 Jan 16 21:54 ..
drwx------ 2 root root 4096 Jan 16 21:52 vol
/mnt/vol:
total 8
drwx------ 2 root root 4096 Jan 16 21:52 .
drwxr-xr-x 3 root root 4096 Jan 16 21:54 ..
-rw-r--r-- 1 root root 0 Jan 16 21:52 base
$ docker start -a child
/mnt:
total 12
drwxr-xr-x 3 root root 4096 Jan 16 21:54 .
drwxr-xr-x 29 root root 4096 Jan 16 21:54 ..
drwx------ 2 root root 4096 Jan 16 21:52 vol
/mnt/vol:
total 8
drwx------ 2 root root 4096 Jan 16 21:52 .
drwxr-xr-x 3 root root 4096 Jan 16 21:54 ..
-rw-r--r-- 1 root root 0 Jan 16 21:52 base
child
$ docker rm data_container
data_container
### the previous command should not have been possible
$ docker start -a child
Error: start: Cannot start container child: Container 7c90924874615b82fb8385310ee2fc45b035cdce32ad14740d031f25417a7e59 not found. Impossible to mount its volumes
2014/01/16 13:54:22 Error: failed to start one or more containers
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
exp/expertkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.