Invalid reference format on launcher rebuild

AI-generated summary

JpMaxMan encountered an “invalid reference format” error during a Discourse launcher rebuild, despite the YAML file being unchanged and the instance having run smoothly for years. The error occurred while stopping and removing containers, with Docker failing due to an invalid repository name format and missing files like cids/app_bootstrap.cid. JpMaxMan also noted that the /pups directory appeared to be missing. As a temporary workaround, restarting the container manually restored the instance. Heliosurge directed JpMaxMan to a relevant thread discussing a similar issue, suggesting it might be related to a removed SSH template. Following this advice, JpMaxMan resolved the problem by commenting out the line templates/sshd.template.yml in the configuration, which allowed the rebuild to proceed successfully. This indicates the error was likely triggered by an outdated or incompatible template reference in the YAML file. The solution highlights the importance of reviewing template configurations after system updates or changes to the Discourse environment.

I am suddenly getting the following error on launcher rebuild. These are for discourse instances that have been running for years without a problem and the YAML file is untouched from the last time that rebuild worked successfully to update discourse. Any help would most sincerely be appreciated.

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.

Also I tried to look in /pups and it indicates there is no such directory?

I am able to get the discourse instance back up and running by simply starting the container again.

Check this thread. It is fixed up. But you might have the issue described.

Thank you!! It appears that commenting out:

templates/sshd.template.yml

fixed this issue.