Race when delete bundle.

[Random-Liu]

$ ctr run -id busybox-2 -t docker.io/library/busybox:latest
/ # exit
$ ctr run -id busybox-2 -t docker.io/library/busybox:latest
/ # exit
ctr: rpc error: code = 2 desc = remove /run/containerd/linux/busybox-2/rootfs: device or resource busy

When Delete a container, it quite frequently fails to delete the bundle with error device or resource busy.
https://github.com/containerd/containerd/blob/master/linux/runtime.go#L140-L144

I'm using naive snapshot plugin. This is very easy to reproduce in my environment, not sure about others.

[miaoyq]

I have a similar issue.
Frequently create and exit containers, sometimes the "ctr run" hangs with error printing ERRO[0000] console resize error="rpc error: code = 2 desc = bad file descriptor, as follow:

# ctr run --id mytest -t docker.io/library/busybox:latest
/ # exit
# ctr run --id mytest -t docker.io/library/busybox:latest
/ # exit
# ctr run --id mytest -t docker.io/library/busybox:latest
ERRO[0000] console resize                                error="rpc error: code = 2 desc = bad file descriptor"
******block here******

# ps -ef |grep mytest
root     10762  7602  0 11:27 pts/1    00:00:00 ctr run --id mytest -t docker.io/library/busybox:latest
root     10803 10770  0 11:27 pts/5    00:00:00 runc --log /run/containerd/linux/mytest/log.json --log-format json start mytest
root     10812 10499  0 11:27 pts/10   00:00:00 grep --color=auto mytest

The status is STOPPED

# ctr ls
ID       PID       STATUS
mytest   10787     STOPPED

[crosbymichael]

@Random-Liu you are using the shim right?

[crosbymichael]

Also how did you run with naive? Are you on OSX or something? Running on linux?

[Random-Liu]

@crosbymichael Yeah, I'm using the shim. And running on linux:

$ uname -a
Linux XXXX 4.4.0-75-generic #96~14.04.1-Ubuntu SMP Thu Apr 20 11:06:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I'm testing on my own desktop, which doesn't have overlay working. So I use the naive plugin.

[crosbymichael]

@miaoyq are you using naive also?

[crosbymichael]

@Random-Liu outside of the naive issue that I'm looking into, how do you not have overlay working on a 4.4 ubuntu kernel? Without having devmapper in containerd, naive is basically the worst option you can pick, its not even compiled into containerd on linux and is no where close to anything that can or should be used in a production/dev setup.

[Random-Liu]

@Random-Liu outside of the naive issue that I'm looking into, how do you not have overlay working on a 4.4 ubuntu kernel? Without having devmapper in containerd, naive is basically the worst option you can pick, its not even compiled into containerd on linux and is no where close to anything that can or should be used in a production/dev setup.

It's a google internal distribution, I've tried that containerd with overlay doesn't work. We won't use naive in the production environment, this is only for my own trial.

Post the issue here because this may be a potential bug.

[miaoyq]

@crosbymichael Yeah, I'm running containerd like this:

containerd --log-level debug

Running on linux also:

Linux ubuntu 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[Random-Liu]

@crosbymichael It's weird that I could not reproduce this anymore... Even with the version I was using...

@miaoyq Do you still have this issue?

[miaoyq]

@Random-Liu Yes, I still can reproduce this issue with the version #819

[crosbymichael]

@miaoyq your error message is totally different and is a separate issue that has to do with IO, not with an EBUSY on the filesystem.

[miaoyq]

@crosbymichael Indeed, I will create a new issue for it.

[Random-Liu]

Close this issue based on:

• Race when delete bundle. #802 (comment)
• Race when delete bundle. #802 (comment)