# How to switch from Docker devicemapper to something less problematic
**URL:** https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894
**Category:** Support
**Created:** [2016年七月6日 09:28 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894 "2016-07-06T09:28:36Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@crowley](https://meta.discourse.org/u/crowley)
#### Post date: [2016年七月6日 09:28 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/1 "2016-07-06T09:28:36Z")
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](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md) around the end of May. Let me know if there is anything I can do to help prevent this for others in the future.
---
### Author:  [@volksman](https://meta.discourse.org/u/volksman)
#### Post date: [2018年八月2日 13:07 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/2 "2018-08-02T13:07:18Z")
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.
---
### Author:  [@crowley](https://meta.discourse.org/u/crowley)
#### Post date: [2018年八月2日 21:54 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/3 "2018-08-02T21:54:49Z")
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 🙂
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018年八月2日 21:56 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/4 "2018-08-02T21:56:39Z")
Can you post/search on [forums.docker.com](http://forums.docker.com) and link the related post here?
---
### Author:  [@volksman](https://meta.discourse.org/u/volksman)
#### Post date: [2018年八月2日 23:00 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/5 "2018-08-02T23:00:58Z")
All good…Found a solution here [Change the Docker storage backend](https://meta.discourse.org/t/how-to-change-storage-backend-in-docker/75352)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2018年八月3日 00:16 UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/6 "2018-08-03T00:16:15Z")