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 rec…

All good…Found a solution here Change the Docker storage backend

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:

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

How to switch from Docker devicemapper to something less problematic

Product Support

volksman August 2, 2018, 1:07pm 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.

Topic		Replies	Views
Change the Docker storage backend Sysadmins docker , how-to	4	23100	October 22, 2024
Upgrade and rebuild reporting I need to use Aufs instead of Devicemapper (on CentOS) Product Support	24	3229	June 19, 2019
(Re)Installing Discourse with Docker on CentOS 7 Self-hosting	6	1855	July 3, 2017
Docker Upgrade Removed AUFS Storage Driver, Killed Discourse Self-hosting	5	962	May 16, 2024
Can't run ./launcher rebuild app - Docker storage driver is unsupported Product Support	71	13736	August 26, 2019

How to switch from Docker devicemapper to something less problematic

Related topics