# Rebuild freezing when attempting to stop container

**URL:** <https://meta.discourse.org/t/rebuild-freezing-when-attempting-to-stop-container/188704>\
**Category:** Self-hosting\
**Created:** [April 30, 2021, 2:12pm UTC](https://meta.discourse.org/t/rebuild-freezing-when-attempting-to-stop-container/188704 "2021-04-30T14:12:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![epskpsdsc](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/epskpsdsc/32/269950_2.png) [@epskpsdsc](https://meta.discourse.org/u/epskpsdsc)\
**Post date:** [August 8, 2022, 2:41pm UTC](https://meta.discourse.org/t/rebuild-freezing-when-attempting-to-stop-container/188704/4 "2022-08-08T14:41:17Z")

</div>

Hey @ajmuir ,  
I know you solved your problem over a year ago but I wanted to add my two cents to this discussion and also enable new users who find this thread to drive down the right path.

Webdock (now) recommends using fuse-overlayfs as the Docker storage driver to use: [How to change the Docker storage driver – Webdock](https://webdock.io/en/docs/how-guides/docker-guides/how-change-the-docker-storage-driver)

Reason being that vfs produces high disk space usage.

But using fuse-overlayfs for Docker will produce a warning or an error on the Discourse launcher side, since it is not a recommended driver.

I have detailed instructions on how to solve this in this post on my blog: [Deploying Discourse on a Webdock server](https://epsilonsynapse.com/webdock/deploying-discourse-on-a-webdock-server/)

You can also do it the way you did by adding the installed driver to the `egrep` statement.

And why do you say that Webdock doesn’t allow the creation of root users?  
You can simply switch to root with `sudo su` and execute the commands from the Discourse install guide after that.

---

_[View the full topic](https://meta.discourse.org/t/rebuild-freezing-when-attempting-to-stop-container/188704)._