# Can't run ./launcher rebuild app - Docker storage driver is unsupported

**URL:** https://meta.discourse.org/t/cant-run-launcher-rebuild-app-docker-storage-driver-is-unsupported/56927
**Category:** Support
**Created:** [February 5, 2017, 12:09am UTC](https://meta.discourse.org/t/cant-run-launcher-rebuild-app-docker-storage-driver-is-unsupported/56927 "2017-02-05T00:09:18Z")
**Posts on this page:** 1
**Showing post:** 41

<div class="post-metadata">

### Author: ![kraml](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kraml/32/68627_2.png) [@kraml](https://meta.discourse.org/u/kraml)
#### Post date: [March 8, 2017, 3:41pm UTC](https://meta.discourse.org/t/cant-run-launcher-rebuild-app-docker-storage-driver-is-unsupported/56927/41 "2017-03-08T15:41:41Z")

</div>

So you are on RHEL 7, which doesn’t have AUFS support. The next recommended storage driver is overlayfs. You need to change the “aufs” parameter in docker.conf to “overlay” or “overlay2”.

And hold on, you probably will run into another problem if you system is installed all by default setting. Check this post for detail.

> [@Bootstrap fails on CentOS 7](https://meta.discourse.org/t/bootstrap-fails-on-centos-7/48927/20):
>
> Most probably it’s because the backing xfs filesystem was not created with ftype=1 option. This is very common if you let the OS installer format the / fs and you just have /var/lib/docker on /. On newer docker verision (1.13?) with docker info you can see support d\_type = false and that indicates your xfs was created with ftype=0 instead of the required ftype=1. This will cause weird issues if you use overlayfs on top of it. See below issues for detail: [https://github.com/docker/docker/issue…](https://github.com/docker/docker/issues/27358)

---

_[View the full topic](https://meta.discourse.org/t/cant-run-launcher-rebuild-app-docker-storage-driver-is-unsupported/56927)._