# Launcher script not updated
**URL:** https://meta.discourse.org/t/launcher-script-not-updated/15688
**Category:** Feature
**Created:** [May 15, 2014, 9:08pm UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688 "2014-05-15T21:08:09Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Greg\_Swallow](https://meta.discourse.org/u/Greg_Swallow)
#### Post date: [May 15, 2014, 9:08pm UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/1 "2014-05-15T21:08:09Z")
I installed discouse on digitalocean via the beginner docker method. I installed updates via the admin/docker url and today updated docker manually to 0.11.1 - I had a problem that the launcher script was not updated and still at the version before this commit here - [Better logic to determine required Docker version · discourse/discourse\_docker@6066840 · GitHub](https://github.com/discourse/discourse_docker/commit/60668406425eeb14bcec9f68cf592cad449a7061#diff-f3e08b5119358a8f58f17a678759f60c) - that didn’t detect 0.11 as a valid version.
Is it a bug that the launcher script wasn’t updated? Or was there something else I should have been doing to update it? I’m sure I had done updates on the admin/docker page more recently than this commit - I actually first installed docker/discourse on May 2nd.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 15, 2014, 9:12pm UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/2 "2014-05-15T21:12:15Z")
Launcher script has to be updated this way, from the command line:
`cd /var/docker`
`git pull`
The web-based updater is a different thing, and you update that via the `discourse.example.com/admin/docker` interface. The updater actually _forces_ you to update it first, if it is out of date.
---
### Author:  [@Greg\_Swallow](https://meta.discourse.org/u/Greg_Swallow)
#### Post date: [May 15, 2014, 10:54pm UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/3 "2014-05-15T22:54:22Z")
I’m fairly certain it was out of date and the updater didn’t force me to run ‘git pull’.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 16, 2014, 12:05am UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/4 "2014-05-16T00:05:12Z")
Can the launcher detect if it is out of date and nag people about the `git pull` @sam?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [May 16, 2014, 12:06am UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/5 "2014-05-16T00:06:43Z")
yes, but I need to figure out how to do it async, don’t want to block it there.
---
### Author:  [@Greg\_Swallow](https://meta.discourse.org/u/Greg_Swallow)
#### Post date: [May 21, 2014, 2:53am UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/6 "2014-05-21T02:53:18Z")
This thread is related - [https://meta.discourse.org/t/keeping-discourse-docker-updated-need-to-manually-git-pull/15290](https://meta.discourse.org/t/keeping-discourse-docker-updated-need-to-manually-git-pull/15290)
I had edited the launcher script so I had to delete it before ‘git pull’ worked. And I then ran destroy/bootstrap/start and all is well again.
If there is an update to the launcher script or another reason to run ‘git pull’ before updating the docker\_manager let me know and I will test if the Docker Manager prompts me to run ‘git pull’ before updating. (edit - or should running ‘git pull’ before updating docker\_manager be part of the documentation?)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 2, 2014, 7:16am UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/7 "2014-06-02T07:16:10Z")
I want to fix this but I do consider this a feature not bug, its rather tricky to get it to work smoothly.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [December 4, 2025, 11:14am UTC](https://meta.discourse.org/t/launcher-script-not-updated/15688/8 "2025-12-04T11:14:24Z")