### Author:  [@fidelio](https://meta.discourse.org/u/fidelio)
#### Post date: [April 11, 2019, 7:20pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/1 "2019-04-11T19:20:48Z")
My Discourse install at Digital Ocean is behaving very oddly. While it is still running fine I can’t do anything via SSH anymore. When I try to enter the container I get the error that the container is not running.
And when I try to rebuild I get:
```
FAILED
--------------------
Pups::ExecError: socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1 failed with return #
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params "socat /dev/null UNIX-CONNECT:/shared/postgres_run/.s.PGSQL.5432 || exit 0 && echo postgres already running stop container ; exit 1"
4f10d0a44bb29a2710b46c2ec2ea7dc2d7b10b8588a1317f0fcac79e32fd95ca
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
What can I do?
Thanks.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 11, 2019, 7:31pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/2 "2019-04-11T19:31:24Z")
Did you add some other container running postgres? Did you rename your `app.yml`?
---
### Author:  [@fidelio](https://meta.discourse.org/u/fidelio)
#### Post date: [April 11, 2019, 7:36pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/3 "2019-04-11T19:36:37Z")
Not really. I added another Droplet but that’s on a different IP.
And I can still enter the app.yml with nano.
---
### Author:  [@fidelio](https://meta.discourse.org/u/fidelio)
#### Post date: [April 11, 2019, 7:52pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/4 "2019-04-11T19:52:50Z")
Actually, I might have created a second container when I was importing some mbox files. I seem to have an app.yml and an import.yml
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 11, 2019, 7:53pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/5 "2019-04-11T19:53:48Z")
You probably need to
```plaintext
cd /var/discourse
./launcher destroy import
```
---
### Author:  [@fidelio](https://meta.discourse.org/u/fidelio)
#### Post date: [April 11, 2019, 8:00pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/6 "2019-04-11T20:00:28Z")
So it seems like the Import container is the one I am now using. Any harm in keeping both containers?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 11, 2019, 8:29pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/7 "2019-04-11T20:29:50Z")
> [@fidelio](#):
>
> Any harm in keeping both containers?
If there isn’t, why are we having this conversation?
What you (probably) want to do is
```plaintext
./launcher stop import
./launcher rebuild app
# make sure that the site is working
./launcher destroy import # so that it doesn't start up when you reboot
# and to be sure that you're not confused in the future
rm containers/import.yml
```
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [July 5, 2022, 2:42pm UTC](https://meta.discourse.org/t/bootstrap-error-when-trying-to-rebuild/114797/9 "2022-07-05T14:42:51Z")