# 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:** Product Support\
**Created:** [6 يوليو 2016، 9: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:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![crowley](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crowley/32/59166_2.png) [@crowley](https://meta.discourse.org/u/crowley)\
**Post date:** [6 يوليو 2016، 9:28ص UTC](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894/1 "2016-07-06T09:28:36Z")

</div>

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.

---

_[View the full topic](https://meta.discourse.org/t/how-to-switch-from-docker-devicemapper-to-something-less-problematic/46894)._