I’m having this problem with
launcher rebuild, where the rebuild is failing, but only after stopping the container.
discourse-doctor is able to resurrect the forum by restarting the old container, but updating it does not seem to be possible currently. I’ve pasted log in the end of the message.
The installation is from September 2016 and currently running Discourse 2.4.1, upgrades for all the pieces have been running fine so far. The host system is Ubuntu 18.04 with latest updates installed and
Docker version 19.03.8, build afacb8b7f0.
Let me know if you need some extra information to better understand the issue. I suppose it would be helpful to add some “printf-debugging” next to the
docker run invocation that’s failing.
$ sudo ./launcher rebuild app Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 10 app app cd /pups && git pull && /pups/bin/pups --stdin /usr/bin/docker: invalid reference format: repository name must be lowercase. See '/usr/bin/docker run --help'. cat: cids/app_bootstrap.cid: No such file or directory "docker rm" requires at least 1 argument. See 'docker rm --help'. Usage: docker rm [OPTIONS] CONTAINER [CONTAINER...] Remove one or more containers rm: cannot remove 'cids/app_bootstrap.cid': No such file or directory ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem.