# 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:** 3

<div class="post-metadata">

**Author:** ![ajmuir](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@ajmuir](https://meta.discourse.org/u/ajmuir)\
**Post date:** [April 30, 2021, 8:22pm UTC](https://meta.discourse.org/t/rebuild-freezing-when-attempting-to-stop-container/188704/3 "2021-04-30T20:22:37Z")

</div>

Thanks Jay, I think I’ve found the issue.

My VPS provider, [webdock.io](http://webdock.io) (who are great by the way) don’t support zfs because they use it at the host level; I’m advised nested zfs is a no go. They also didn’t recommend overlay2 for my install and suggested I edit `launcher` to include the **vfs** storage driver, which isn’t there by default.

171‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ `Storage Driver: (vfs|aufs|zfs|overlay2)`  
‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎‎‏‏‎ ‎‏‏‎ ‏‏‎‎‏⬆️

I suspect `sudo git pull` overwrote this, and then I tried to rebuild with the wrong storage driver?

I’ve just rolled everything back and then re-edited `launcher` before running `rebuild app` and everything is working again.

```
cd /var/discourse
sudo git stash
sudo git pull
sudo nano launcher 

```

‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ then edit line 171 to include **vfs**

`sudo ./launcher rebuild app`

---

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