On the forum I use as a test bed, I just did some normal maintenance routines, and now I get this error during a rebuild
Removing old container
+ /usr/bin/docker rm app
Error response from daemon: Driver aufs failed to remove root filesystem b610111d39e8634398cd28b510bf362b09640e9111438503c12d22b3cd046950: rename /var/lib/docker/aufs/mnt/2b8f3dac5f82f25dfbc6a17d9c0fd70aca12cace46fc72be6090eb3554c99886 /var/lib/docker/aufs/mnt/2b8f3dac5f82f25dfbc6a17d9c0fd70aca12cace46fc72be6090eb3554c99886-removing: device or resource busy
starting up existing container
+ /usr/bin/docker start app
Error response from daemon: Container is marked for removal and cannot be started.
Error: failed to start containers: app
Prior to this, I ran apt-get upgrade, which netted Docker version 17.04.0-ce, build 4845c56
This is a digitalocean ubuntu 14.0.4 LTS droplet using the standard docker install.
History tells me there’s a problem with my kernel & image extra versions.
Why not use a 16.04 image? Also you could give the output of uname -r – which would be immensely helpful here but I’d recommend just updating to 16.04 unless you have a reason to be on 14.04
This has been 14.04 since I installed it a while back… I could upgrade to 16, but will that stop the mysterious aufs issues which have come up from time to time?
Yup, it certainly will! I’ve been sysadmin for two discourse installs, so can vouch for it not sucking. Just ensure you follow the docker install instructions.
This has always been an odd problem to me since the official install guide says to use the wget command from get.docker.com to install Docker. And I have never observed this problem on any install we did, which obviously follows the official guide slavishly.
wget -qO- https://get.docker.com/ | sh
So this implies people who do have this problem installed Docker in some oddball, non-install-guide way… somehow.
I dunno about the docker aspect… this instance has been running fine for over a year, through other docker upgrades even.
Today I did apt-get upgrade and I got fussed at about a lack of aufs. I don’t even think it was a docker issue, but a mismatch of kernel & image-extra. If ubuntu 16 resolves that issue, I’m going to put image-extra out of my life with an OS upgrade.
Still something super hinky with this as we literally never saw this problem with hundreds of official guide based installs across a period of literally years. Did you add any “extra” stuff or steps?
(I agree it has been reported on meta a few times but I strongly suspect “extra” things were done…)