Aha, I see. That explains why the output of docker ps was empty - I was running that on my host (Torizon under WSL2). When I connected the device with “Set Default” and restarted my terminal, then docker ps is showing me the containers running on the device.
OK, yes, I’m still getting the message ❌ Docker container registry is not running!
The root of it seems to be that I can’t start the registry container in Torizon on WSL. So we’re back to what I shared a couple messages ago:
First, trying to run the registry container (on host, not device) says it already exists:
docker run -d -p 5002:5000 --restart=always --name registry registry:2
docker: Error response from daemon: Conflict. The container name "/registry" is already in use by container "7d3abc5ca17db27b68957b33865cf2d231c852050e612d3d95339e47e4ad67ab". You have to remove (or rename) that container to be able to reuse that name.
Run 'docker run --help' for more information
So I remove it as you instructed:
~: docker container rm -vf registry
registry
And try to run it again:
~: docker run -d -p 5002:5000 --restart=always --name registry registry:2
a47ff4627c6307e0342069f41f9ef91bbf196537ada6c34dfc26e9e084b99a24
docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint registry (8a2f107c8d5dd478586239a46c95944fa4104334d7bdad466fe331607389f807): failed to bind host port for 0.0.0.0:5002:172.17.0.2:5000/tcp: address already in use
Run 'docker run --help' for more information
This indicates the port is already in use. No containers are running:
~: docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES