[aufs] Unable to delete a container when / partition is mounted #18509
Comments
|
I have also tested it in docker 1.9.1 and it is a problem as well. |
|
Thanks for reporting @jeanpralo, just to check; is this a regression since 1.8? Were you able to do this in 1.8 without issues? |
|
@thaJeztah I have just been able to reproduce using docker 1.8.3 and 1.7.1 so it has been around for quite a while now. |
|
@jeanpralo thanks for checking. |
|
In that output; is |
|
@thaJeztah it's the id of the second container started in step 2 |
|
@thaJeztah will you be assigning any labels on that issue ? Just want to know what sort of timeframe it will be consider to fix that issue as it is quite a problem especially when using a container to get metrics from servers ( i use collectd in a container to get metrics out of my servers so for the df plugin i need to mount / ) :) Thank you :) |
thaJeztah
added
the
kind/bug
|
@jeanpralo I added a "bug" label. I can't give you an estimate as to when this will be looked into. I just tried to reproduce, but I'm unable to reproduce this 😢 I tried these steps; $ docker run -d --name looper -v /:/check:ro ubuntu /bin/sh -c 'while true; do echo foo; sleep 1; done'
60233ec48b4d64456405ec6a633270594a9964f70e969e0b2432075158e5c162
$ docker run -it --rm ubuntu
root@df9fa8750296:/#in a second shell: first shell: root@df9fa8750296:/# exit
exit |
|
@thaJeztah are you using aufs or devicemapper as a storage driver. I have been able to reproduce that problem only with aufs so far, no problem with devicemapper. |
jeanpralo
changed the title
|
That was on aufs. I can try it on some other hosts |
|
@thaJeztah I was able to reproduce on aws ec2 choosing the latest ubuntu AMI. From a fresh install i ran those commands: Inside the screen I run: 1- Create the looping container mounting / 2- Start a fresh container with a shell interactively 3- Restart the looper container 4- Try to exit and it fails Note that the container stays with a status
|
|
I imagine this is because there are mounts leaking into the container by mounting in |
|
So basically we need to avoid to mount anything which is /var/lib/docker related ? Is this something fixable or we need to find a workaround to that problem, sorry I have not read much about aufs. |
|
I don't think this is AUFS related in particular. Can you try with master? |
|
@cpuguy83 I am testing with the latest compiled binary from https://master.dockerproject.org/, never really debugged in docker before so tell me if I have to compile it directly from master. The problem is not exactly the same anymore seems like there is a problem with the shared memory mountpoint now: I have followed the exact same step as before.
|
|
I'm getting the same bug. docker info: |
|
I've just encountered this bug as well. Is there a workaround? |
|
@sjackman that looks like a whole different issue, more likely something on your system; |
|
Rebooting the virtual machine resolved the issue. |
|
+1
Server:
|
|
@ghasemz looks like you're not running an official binary; it's built from modified source (see "git commit" in your output); did you build it yourself? |
|
@thaJeztah have you been able to reproduce on aws ? Just wondering if I am the only one having the issue so far :) |
|
+1 for receiving this error as well.
Server:
@jeanpralo I was getting the shared memory bug you mentioned above and just like your output, I was on kernel 3.13. I upgraded to 3.16, uninstalled/reinstalled docker, and now started receiving this error. |
|
Also to note, I'm running all my containers on a named network. I wonder if this issue is due to linking between the containers? Maybe this was already mentioned. |
|
I also have the same problem: Client: Server: Ubuntu 14 Can't remove some containers without restarting the main docker profess. And when its restarted, seems like containers are garbage collected. Any workaround, or solution? |
|
@jordic out of curiosity, what kernel version are you running? |
|
3.13.0-79-generic |
|
@jordic at one time I thought it had to do with the kernel version, but now, I'm not so sure. We're on 3.16 and sometimes still experience this issue. |
|
Same issue here: Docker Client 1.11.0 The container is marked as Dead. I don't know if it can help, but when I try to restart it with |
|
@Teudimundo are you running cadvisor on the docker host? |
|
No cadvisor, that container in particular was just a |
|
Same issue with version Docker version 1.10.3, build 20f81dd Solved unmounting the dir: I'm not sure it's ok what I did ... but it worked! ;) |
|
Same issue in docker 1.10.3 on Ubuntu 14.04 64 bits. The kernel is |
|
I'm having the same problem on RHEL 7.2. ErrorCan't unmount that... OSDocker Info |
|
This happened to me on Ubuntu 14.04 with docker-compose when I attempted to bind mount the volume /dev/log:/dev/log:rw. |
|
The AuFS storage driver has been deprecated and has been removed from our code base (#45342) for the upcoming v24.0.0 release, so we're closing tickets related to AuFS |
Hi guys,
BUG REPORT INFORMATION
docker version:Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.2
Git commit: 76d6bc9
Built: Tue Nov 3 17:43:42 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.2
Git commit: 76d6bc9
Built: Tue Nov 3 17:43:42 UTC 2015
OS/Arch: linux/amd64
docker info:Containers: 11
Images: 181
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 205
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-43-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 1
Total Memory: 987.9 MiB
Name: ch-lundi3
ID: CVYX:O4VO:FX57:K7JU:PG6N:DZRV:GXW7:XN2E:4LUO:QSF4:B2YJ:CYRZ
WARNING: No swap limit support
uname -a:Linux ch-lundi3 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce the problem
1- docker run -d --name lafauteaqui -v /:/check:ro ubuntu:14.04 /bin/sh -c 'while true; do echo la_faute_a_flop; sleep 1; done'
2- docker run -it --rm ubuntu:14.04
3- docker restart lafauteaqui
4- Try to exit the shell in the container started during step2:
Describe the results you received:
It should exit gracefully
The text was updated successfully, but these errors were encountered: