Launcher [rebuild/start/stop] app throwing error


(Neil) #1

Hello there,

My Discourse installation has been running fine for about a week now.
Tonight, I made some changes to app.yml and ran the familiar ./launcher app rebuild command only to be met with this response

Unable to find image 'discourse/discourse:1.3.10' locally
Pulling repository docker.io/discourse/discourse
/usr/bin/docker: Tag 1.3.10 not found in repository docker.io/discourse/discourse.
See '/usr/bin/docker run --help'.
Your Docker installation is not working correctly

After trying to troubleshoot the error via various posts here on meta, I’m a little stumped.
I get the same message whether I try launcher stop app, launcher cleanup etc. Basically, no launcher command will work right now.

I checked https://hub.docker.com/r/discourse/discourse/tags/ and tag 1.3.10 is indeed not there. I believe this is the problem, but my docker/discourse knowledge is not sufficient enough for me to solve it myself.

Just for info, I tried docker pull discourse/discourse:1.3.9 and the return message is

Status: Image is up to date for discourse/discourse:1.3.9

I’m sure I’m just missing a parameter here to fix this. Can anyone help me out?

Thanks in advance,
Neil.


Tag 1.3.10 not found on reload
Docker error on Bootstrap
(Rafael dos Santos Silva) #2

My bad, bumped image too early and got bit by a subtle change on google brotli. Pushing image now, will inform here when fixed.


(Brady) #3

Just ran ./launcher rebuild app and in return I got:

Unable to find image 'discourse/discourse:1.3.10' locally
Pulling repository docker.io/discourse/discourse
/usr/bin/docker: Tag 1.3.10 not found in repository docker.io/discourse/discourse.
See '/usr/bin/docker run --help'.
Your Docker installation is not working correctly

With the reference to this thread. Looks like this is because the image was just barely updated but hasn’t been posted to Docker hub so as @riking mentioned, the solution is just to wait an hour or so and then run the command again.

Any thoughts are welcome if that’s not the case.

In the meantime, can/should I force it to use 1.3.9? If so, how?


(Rafael dos Santos Silva) #4

1.3.10 is live on docker hub. Sorry about it :sadpanda:


(Neil) #5

Rebuilding now. Thanks :slight_smile:


(Jeff Atwood) #6