Launcher cleanup side effect - bad?


(Scott Smith) #1

I ran launcher cleanup a week or so ago (./launcher cleanup). Today I used launcher for the first time since and got:

./launcher

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

Unable to find image 'discourse/discourse:1.3.5' locally
1.3.5: Pulling from discourse/discourse
Digest: sha256:a3fffe0bc4a462c52429e4986932a1733be384f9211e7e48f14864bd9306fb53
Status: Downloaded newer image for discourse/discourse:1.3.5

and since I didn’t know where this could be going I hit control-C at this point. Should I just let this run?

PS I do have 1.3.5 in fact. 11 days ago is probably when I did the cleanup.

# docker images
REPOSITORY             TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
local_discourse/app    latest              0bab02d52341        7 days ago          1.65 GB
discourse/discourse    1.3.5               857ef7ee248e        11 days ago         1.501 GB
samsaffron/docker-gc   latest              c8534add8475        7 months ago        57.64 MB

If I do ./launcher command app --skip-prereqs I can still run the other launcher commands now on the currently running container.

PPS Hey it looks like all is fine now… I did ./launcher again and no warning message. I guess it was just a glitch.


(Martial) #2

Well, there is nothing bad to downloading the Discourse image based if it’s not present, why hit ctrl-C ?


(Scott Smith) #3

If I knew more I probably wouldn’t have minded. I was concerned it was thinking I was starting all over and would start resetting things after image download.


(Allen - Watchman Monitoring) #4

vaguely reminds me of this, when I saw the same image downloaded twice…

but, maybe you just didn’t have 1.3.5 yet?