# Rebuild failed - FAILED TO BOOTSTRAP

**URL:** https://meta.discourse.org/t/rebuild-failed-failed-to-bootstrap/289514
**Category:** Self-hosting
**Created:** [December 22, 2023, 5:21am UTC](https://meta.discourse.org/t/rebuild-failed-failed-to-bootstrap/289514 "2023-12-22T05:21:25Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![Firepup650](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/firepup650/32/465200_2.png) [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [December 22, 2023, 6:01am UTC](https://meta.discourse.org/t/rebuild-failed-failed-to-bootstrap/289514/4 "2023-12-22T06:01:41Z")

</div>

From another topic on this exact issue:

> [@Update Fails with Unexpected Error During Rebuild](https://meta.discourse.org/t/update-fails-with-unexpected-error-during-rebuild/288718/12):
>
> Jay had the same issue [Rebuild failure: "extconf failed, exit code 1" -- due to old Docker?](https://meta.discourse.org/t/rebuild-failure-extconf-failed-exit-code-1-due-to-old-docker/287756), but I don’t know if he figured out the issue ultimately. @TroyaNO Just in case, can you try to type git pull before trying again ./launcher rebuild app?

> [@Update Fails with Unexpected Error During Rebuild](https://meta.discourse.org/t/update-fails-with-unexpected-error-during-rebuild/288718/13):
>
> I decided that it was an old Docker, though that didn’t really make sense. But I bet this has been on the same vm since 2018 and the os is out of date. So what I would do is spin up a new droplet and [Move a Discourse site to another VPS with rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812).

---

_[View the full topic](https://meta.discourse.org/t/rebuild-failed-failed-to-bootstrap/289514)._
