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. uname -r tells me 3.13.0-71-generic I also see :/var/discourse# dpkg --get-selections | grep linux-image linux-image-3.13.0-105-generic deinstall linux-image-3.13.0-106-generic deinstall linux-image-3.13.0-107-generic deinstall linux-image-3.13.0-108-generic deinstall linux-image-3.13.0-57-generic deinstall linux-image-3.13.0-61-generic deinstall linux-image-3.13.0-68-generic deinstall linux-image-3.13.0-71-generic install linux-image-3.13.0-74-generic deinstall linux-image-3.13.0-76-generic deinstall linux-image-3.13.0-77-generic deinstall So, I guess I’m missing the one image that matches my kernel? I guess my question here is.. how best to avoid issues like this, where I’m dealing kernel mis-matches? (Unless, of course, there’s some other issue like a known problem in docker, etc) TIA

I ran discourse just fine on 14.04…i’m confused Have you done: sudo apt-get install \ linux-image-extra-$(uname -r) \ linux-image-extra-virtual from the installation guide?

You don’t need to upgrade now…you won’t have an issue…but you REALLY should at some point :slight_smile:

Upgrade now, when I’m ready for issues? Or when some random apt-get upgrade will stop the show? Hahaha, thanks, this is plenty reason to start the process of upgrading.

[תמונה] watchmanmonitor: Upgrade now, when I’m ready for issues? Or when some random apt-get upgrade will stop the show? Hahaha, thanks, this is plenty reason to start the process of upgrading. You didn’t install a package dependency, which is in the docker installation guide… that’s what caused your problem.

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.

This is the start of this host’s .bash_history sudo install -o root -g root -m 0600 /dev/null /swapfile dd if=/dev/zero of=/swapfile bs=1k count=1024k mkswap /swapfile swapon /swapfile echo "/swapfile swap swap auto 0 0" | sudo tee -a /etc/fstab sudo sysctl -w vm.swappiness=10 echo vm.swappiness = 10 | sudo tee -a /etc/sysctl.conf wget -qO- https://get.docker.com/ | sh mkdir /var/discourse cd /var/discourse git clone https://github.com/discourse/discourse_docker.git /var/discourse ls -al vi containers/app.yml apt-get update

[תמונה] codinghorror: wget -qO- https://get.docker.com/ | sh Didn’t docker silently deprecate this method?

Too bad it didn’t include a trigger to always add the kernel’s related image-extras package.

[תמונה] codinghorror: Nope try it yourself and see. It works – but it could stop working at any time is what I mean.

בעיות עם docker והקטע ליבה ב-digital ocean

תמיכה התקנה

robbyoconnor (Robby O'Connor) 8 באפריל,‏ 2017,‏ 6:40am 18

this – I actually use ansible to install docker in almost all cases.

נושא		תגובות	צפיות
Ubuntu updates intefere with Docker and AUFS? Self-hosting	17	14723	2 במרץ,‏ 2016
Device 'docker0' missing after system upgrade? Self-hosting	26	5511	22 בדצמבר,‏ 2016
Will not load, no access to installation, aufs not installed - my fix Self-hosting docker	3	2144	17 בפברואר,‏ 2015
Docker install: Module aufs not found Self-hosting	14	24234	21 באוגוסט,‏ 2014
"ignoring file '50unattended-upgrades.wcf-dist' in directory '/etc/apt/apt.conmf.d/' as it has an invalid filename extension Self-hosting	18	3745	20 בפברואר,‏ 2017

בעיות עם docker והקטע ליבה ב-digital ocean

נושאים קשורים