How to switch from Docker devicemapper to something less problematic


#1

So, in the process of recovering from a disk-full situation during an otherwise normal Discourse upgrade, I realized that we are apparently using the “devicemapper” Docker storage driver, which seems to be heavily discouraged for Discourse, as I gather from other threads here.

What would be the recommended procedure to fix that and use the recommended driver instead (aufs, right?) – backup/reinstall/restore, or is there an easier way? This is on an EC2 instance with AMI Linux 2016.03 and Docker v1.11.1.

And on a more general note: I stumbled upon this devicemapper thing pretty much accidentally; according to other threads, it shouldn’t even have been possible to set up Discourse this way? I may have missed a warning fly past, but I’m sure I did not deliberately override anything during the installation process. I set it up according to the guide on GitHub around the end of May. Let me know if there is anything I can do to help prevent this for others in the future.


#2

Any solution found here? I seem to be in the same boat. I have a fairly large community running on this and looking to upgrade.


#3

I didn’t find one… that (very small) Discourse installation worked fine while it lasted, but it’s long gone now, and I haven’t touched AMI Linux since then :slight_smile:


(Sam Saffron) #4

Can you post/search on forums.docker.com and link the related post here?


#5

All good…Found a solution here How to change storage backend in Docker


(Sam Saffron) #6