# Install v1.7.2 using Docker
**URL:** https://meta.discourse.org/t/install-v1-7-2-using-docker/59635
**Category:** Development
**Created:** [March 21, 2017, 5:50pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635 "2017-03-21T17:50:12Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Kel](https://meta.discourse.org/u/Kel)
#### Post date: [March 21, 2017, 5:50pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/1 "2017-03-21T17:50:12Z")
Hi there,
First post so hello š
I am trying to install Discourse on a Digital Ocean Droplet all goes well, except I need to run a script that only works with v1.7.2 (long story just trust me!)
Tried everything I can think of to get Docker to do a clean install of v1.7.2 - does anyone know the correct procedure please?
Any help would be very much appreciated.
Kind regards
Kel
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 21, 2017, 5:54pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/2 "2017-03-21T17:54:26Z")
In `app.yml` where it says ātests-passedā you can put the the Git ID of the version you want.
So I think you want
```
version: 839a5e6e427bdffb87596f8fbe51c37796e40da3
```
`version` is in the file, but commented out.
---
### Author:  [@Kel](https://meta.discourse.org/u/Kel)
#### Post date: [March 21, 2017, 5:59pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/3 "2017-03-21T17:59:06Z")
Thanks!
I searched and found that solution earlier (it works using āv1.7.2ā) but it seems to be only be able to do that as a rebuild the .yml file doesnāt exist until after the newest version has been installed.
These are the instructions I followed:
[discourse/docs/INSTALL-cloud.md at main Ā· discourse/discourse Ā· GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)
I need to be able to change the version number between the install and the setup.
All I have managed to do so far is install and then downgrade, thatās not what I am looking for.
The reason for this is that there seems to be some kind of database incompatibility with the script I am trying to run and the rebuild doesnāt fix it - although this is a guess!
I feel like I am missing something obvious.
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [March 21, 2017, 6:31pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/4 "2017-03-21T18:31:12Z")
You can create `app.yml` manually (there is a template in `/var/discourse/samples/standalone.yml`) ā but if you already bootstrapped and want to downgrade, this is easy as long _as you are willing to lose your data_. Simply update `app.yml`, then run this:
```bash
cd /var/discourse/
./launcher stop app
rm -rf shared/standalone/ # wipe shared volume
./launcher rebuild app
```
> ā Executing these commands will **completely reset Discourse**! All content, users and settings will be deleted.
---
### Author:  [@Kel](https://meta.discourse.org/u/Kel)
#### Post date: [March 21, 2017, 6:32pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/5 "2017-03-21T18:32:50Z")
> [@fefrei](#):
>
> rm -rf shared/standalone/ # wipe shared volume
I defintiely want to lose the data, everything needs to go so itās a complete fresh installā¦
This is probably what I was missing - thank you!!!
Iād done everything but this one line!!!
Thank you!!!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 21, 2017, 6:32pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/6 "2017-03-21T18:32:58Z")
You can `cp samples/standalone.yml containers` and edit it by hand, or use `./discourse-setup` and hit a control C after itās through configuring. Thereās an undocumented 5 second pause before it starts the build, for just that purpose.
---
### Author:  [@Kel](https://meta.discourse.org/u/Kel)
#### Post date: [March 21, 2017, 6:51pm UTC](https://meta.discourse.org/t/install-v1-7-2-using-docker/59635/7 "2017-03-21T18:51:20Z")
Brillaint, this is the magic dust I was looking for and couldnāt find š
I am already rebuilding and know itās working as Iāve seen all the database commands run again - so have a lot of confidence I am going to end up with a 1.7.2 and corresponding database!
We will see, I will let you know!
Thanks again š