# Destroying docker container does not destroy the database?

**URL:** <https://meta.discourse.org/t/destroying-docker-container-does-not-destroy-the-database/26411>\
**Category:** Self-hosting\
**Created:** [2015 年 3 月 16 日午後 9:18 UTC](https://meta.discourse.org/t/destroying-docker-container-does-not-destroy-the-database/26411 "2015-03-16T21:18:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jamesmarkcook](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jamesmarkcook/32/168563_2.png) [@jamesmarkcook](https://meta.discourse.org/u/jamesmarkcook)\
**Post date:** [2015 年 3 月 16 日午後 10:13 UTC](https://meta.discourse.org/t/destroying-docker-container-does-not-destroy-the-database/26411/4 "2015-03-16T22:13:23Z")

</div>

> [@sam](#):
>
> By design, all data is stored out of the container in a volume.

Thanks Sam. I don’t think I ever would have figured that one out.

Is this something specific to the Discourse install, or is this a Docker feature?

But yes, @brahn has a point. Shouldn’t `./launcher destroy app` do this for you?

If not, I think it’s at least something to highlight on the install guides for anyone following along, as the destroy command would give the impression that you’re starting fresh.

---

_[View the full topic](https://meta.discourse.org/t/destroying-docker-container-does-not-destroy-the-database/26411)._