The thread discusses the mysterious “cool_kepler” docker image. AstonJ initially noticed it while running docker container ls -a and suspected it may be related to issues they were experiencing. supermathie explained that docker assigns random names to unnamed containers and suggested checking its logs with docker logs -t bb928f3612cb. AstonJ removed the image with ./launcher cleanup, reclaiming 35GB, and attributed its presence to an aborted rebuild.
Just ran docker container ls -a and noticed something weird:
bb928f3612cb discourse/base:2.0.20231218-0429 "/bin/bash -c '/usr/…" 2 weeks ago Exited (0) 2 weeks ago cool_kepler
All the other docker images are my discourse forums, but I don’t recognise this one - it also seems to have been created when I started experiencing other issues.
“unnamed” docker containers get a random name assigned to them, e.g.:
○ → docker run -it debian:latest
root@106e6c22914a:/# exit
○ → docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS NAMES
106e6c22914a debian:latest "bash" 33 seconds ago Exited (0) 29 seconds ago silly_rhodes
please allow me to present for your entertainment my favourite example of this:
If you’re curious what it did you can check its logs: docker logs -t bb928f3612cb
but it should be safe to remove; it may have been left when you aborted a rebuild.
Thanks, I removed it with ./launcher cleanup and reclaimed 35GB 
That makes sense - a rebuild hanged so had to be aborted.