# "Your Docker installation is not using a supported storage driver."

**URL:** <https://meta.discourse.org/t/your-docker-installation-is-not-using-a-supported-storage-driver/124131>\
**Category:** Self-hosting\
**Created:** [7월 27, 2019, 2:15오후 UTC](https://meta.discourse.org/t/your-docker-installation-is-not-using-a-supported-storage-driver/124131 "2019-07-27T14:15:02Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [7월 27, 2019, 5:55오후 UTC](https://meta.discourse.org/t/your-docker-installation-is-not-using-a-supported-storage-driver/124131/7 "2019-07-27T17:55:59Z")

</div>

Well, long story.

Docker 19.x changed the whole structure of the `docker info` output.

We fixed that when 19.x was still on the beta branch more than a month ago at [FIX: Make storage detection compatible with docker 19.x · discourse/discourse\_docker@98c5fec · GitHub](https://github.com/discourse/discourse_docker/commit/98c5fec43de299bdfc55970cea3495fa4c27d6ac). The fact that our launcher script auto-updates makes this a non-issue for most people.

However, our `launcher` script checks for the storage compatibility before auto-updating. So people who have an old launcher and update docker before updating launcher can get into that state.

---

_[View the full topic](https://meta.discourse.org/t/your-docker-installation-is-not-using-a-supported-storage-driver/124131)._