This was going fine for me until the last moment, when I got the following super-useful error message: Error response from daemon: Cannot destroy container 1cd705ffc49f5ce0622614316e3a742b8e6c8a77362528338db30a6f352477d2: Driver devicemapper failed to remove root filesystem 1cd705ffc49f5ce062261431…

[image] Manually update Discourse and Docker image to latest but you are on your own here I’m using the standard “by the book” installation using the docs provided here and a Digital Ocean server, as recommended.

Nope, device mapper is not supported, never was. You MUST get aufs working.

[image] Manually update Discourse and Docker image to latest Nope, device mapper is not supported, never was. You MUST get aufs working. I have no idea what either of those are. I only followed the official directions for the docker installation, and the only changes we’ve made were to add SSL…

Looks like I have the same problem reported here: https://meta.discourse.org/t/discourse-did-not-restart-after-system-crash/24494/5?u=downey So be careful installing normal updates to your OS, apparently it breaks Discourse. :stuck_out_tongue:

Supposedly docker 1.5 will make device mapper more reliable, on the fence on this cause I heard this many time before.

I am curious, how were you updating Ubuntu? I tend to update Docker on mine every few months so perhaps that’s why I didn’t see any regression on kernel / aufs: apt-get update apt-get dist-upgrade lxc-docker

I think to recover, you’ll have to manually docker rm/rmi the leftovers, then rebuild. Quick overview of that: docker images -a # identify useless images (old discourse base, untagged), then docker rmi d25ec275fb1d 818beea55263 cdb5237bc8a7 docker ps -a # identify dead/defunct containers, then do…

[image] codinghorror: I am curious, how were you updating Ubuntu? Just using apt-get upgrade and upgrading all packages every few weeks. As mentioned in the other thread, it’s hard to say when aufs went away, it was surely in a kernel upgrade at some point, and then this is likely the first …

Hi folks. I’ve hit that snag too. Basically, ensure you have linux-image-extra-virtual and aufs-tools installed add to /etc/default/docker something like this DOCKER_OPTS="-s aufs" I wrote a blog post about it here but the steps above is all you need. really.

Ubuntu updates intefere with Docker and AUFS?

Support Self-hosting

sam (Sam Saffron) February 9, 2015, 8:22pm 2

Device mapper is not supported, please get aufs working.

You could probably recover by rebooting, but you are on your own here.

Topic		Replies	Views
Will not load, no access to installation, aufs not installed - my fix Self-hosting docker	3	2123	February 17, 2015
Problems with docker and kernel on digital ocean Self-hosting	24	4438	April 10, 2017
Device 'docker0' missing after system upgrade? Self-hosting	26	5422	December 22, 2016
Docker Upgrade Removed AUFS Storage Driver, Killed Discourse Self-hosting	5	955	May 16, 2024
Not Using A Supported Storage Driver Support unsupported-install	36	3947	May 3, 2017

Ubuntu updates intefere with Docker and AUFS?

Related topics