Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
docker-17.06.1-ce: error creating overlay mount to /var/lib/docker/overlay2/ID/merged: device or resource busy" #2127
Container Linux Version
Current nightly test runs, e.g.:
Happens on qemu and AWS, probably all of them.
Every once in a while, the first run has the below error:
We, unfortunately, bumped the kernel to 4.13 at around the same time we bumped docker to 17.06.
This happens very infrequently. When it does happen, the impact is minimal; the first container run fails, but subsequent ones are fine. I think it can only happen as the first container run, so anything that's retrying appropriately should be fine.
There's also an overlayfs related message in
Full dmesg below:
That printk message, and resulting mount error, are introduced in https://patchwork.kernel.org/patch/9760547/
That's new to the 4.13 kernel.
It seems very likely to me docker internally has a race or logic bug resulting in it mounting twice in some cases, and until now it silently succeeded.
@euank there has been a failure in the process handling this regression.
As I read the patch, it seemed like it was intentionally preventing this behavior for the sake of correctness, which isn't so much breaking userspace as "userspace was already broken, let's make it more obvious".
Regardless, I'm glad you've found your way to this info even though we neglected to email you. Thanks for the help!
@euank you should read https://felipec.wordpress.com/2013/10/07/the-linux-way/
Your work to fix docker is important none the less.
Secondly, at some point, it is hoped, docker will want to catch up with new overlayfs features
Thanks for testing early versions and reporting the issue!