Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
d6f04ca979800ae6938c231f5ec57316431b6cbbe358bd1c843fcc1f94db984a
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
I have tried rebuilding multiple times and I’ve tried completely destroying the installation and starting again but it always fails this way. Changing the branch back to tests-passed allows the rebuild to complete.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [1 Gennaio 2018, 4:16pm UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/2 "2018-01-01T16:16:57Z")
We don’t support downgrades, so to move to stable you need to start on a brand new install.
---
### Author:  [@Philip\_Colmer](https://meta.discourse.org/u/Philip_Colmer)
#### Post date: [2 Gennaio 2018, 7:46am UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/3 "2018-01-02T07:46:08Z")
I’ve tried it on a brand new install. I deleted the Discourse directory, pruned Docker of any existing images, cloned the git repository, edited app.yml to specify the desired branch and it will not build.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2 Gennaio 2018, 7:46am UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/4 "2018-01-02T07:46:58Z")
The database storage is outside the container, though, and it looks like you didn’t nuke that?
---
### Author:  [@Philip\_Colmer](https://meta.discourse.org/u/Philip_Colmer)
#### Post date: [2 Gennaio 2018, 8:03am UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/5 "2018-01-02T08:03:44Z")
OK … that is a possibility, although if it isn’t stored within /var/discourse (or whereever the git repository gets cloned), where is it stored since I haven’t specified another path?
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [2 Gennaio 2018, 10:50am UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/6 "2018-01-02T10:50:16Z")
It should be in there. Try this:
1. `cd /var/discourse`
2. Stop the container in case it is still running: `sudo ./launcher stop app`
3. Delete the database: `sudo rm -rf shared/standalone/`
⚠ This step will delete all Discourse-related data!
4. Make sure `app.yml` is on the stable version
5. Run `sudo ./launcher rebuild app` to bootstrap and start the container, which will create a fresh database
The important thing is not to bootstrap any newer version before having selected `stable`, or deleting the `shared` folder in-between – anything else would be a downgrade of a (mostly empty) Discourse database, which is unsupported.
---
### Author:  [@Philip\_Colmer](https://meta.discourse.org/u/Philip_Colmer)
#### Post date: [2 Gennaio 2018, 1:39pm UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/7 "2018-01-02T13:39:30Z")
I’ve realised where I’ve been going wrong … the yml config file references “/var/discourse/shared” but we’re actually using /srv/discourse … so I forgot to update those paths.
Now that I’ve sorted that all out (and properly removed the previously build database), I can correctly set up Discourse on the stable branch.
Sorry for the noise 🙂
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2 Gennaio 2018, 10:16pm UTC](https://meta.discourse.org/t/stable-branch-will-not-downgrade-fails-on-db-migrate/77049/8 "2018-01-02T22:16:47Z")