# Rebuild taking ~3hours

**URL:** <https://meta.discourse.org/t/rebuild-taking-3hours/240859>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [October 4, 2022, 6:11am UTC](https://meta.discourse.org/t/rebuild-taking-3hours/240859 "2022-10-04T06:11:54Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [October 4, 2022, 10:10am UTC](https://meta.discourse.org/t/rebuild-taking-3hours/240859/15 "2022-10-04T10:10:07Z")

</div>

Because it’s easier than doing what you really need to do.

> **[Select a storage driver](https://docs.docker.com/engine/storage/drivers/select-storage-driver/)**
>
> Learn how to select the proper storage driver for your container.

> [@](#):
>
> The `vfs` storage driver is intended for testing purposes, and for situations where no copy-on-write filesystem can be used. Performance of this storage driver is poor, and is not generally recommended for production use.

Adding swap might help, but it’s not your biggest issue.

---

_[View the full topic](https://meta.discourse.org/t/rebuild-taking-3hours/240859)._