SSH works, but no Web Interface after power loss

Support and Troubleshooting
1

We had an unscheduled power outage in our neighborhood last night. This morning when I checked all my systems, I found that i could not load the web interface of my Umbrel (Raspberry Pi 4. running version 0.5.4) I can ping the device, and successfully login via SSH, but the debug script (/home/umbrel/umbrel/scripts/debug) shows the following. How can I check/restart the Docker daemon?

Any suggestions appreciated.

Harry Pilgrim

Docker containers
-----------------
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Umbrel logs
-----------

./debug: line 131: docker-compose: command not found

Tor Proxy logs
--------

./debug: line 137: docker-compose: command not found
This script requires "docker-compose" to be installed
2

I had this issue about 18 months ago and posted my solution to the Umbrel Support Telegram, but that channel seems to have been closed down, or else maybe I’m blocked?

As I recall, I needed to manually remove Docker images and I think reinstall my Docker packages. I think it went something like this:

  1. apt list --installed | grep -i docker to find any installed Docker packages.
  2. Then I did an apt remove command to uninstall all those Docker packages.
  3. Then I did a apt-get install command to reinstall all those Docker packages.
  4. At this point, I would have done a sudo reboot to restart the system, and I think at this point, I got a Web server to respond, but all of the apps failed to boot, including the Umbrel GUI.
  5. Now, I did a docker ps to find any running containers.
  6. Then I used some docker container stop commands to stop any running images - I think there were almost none at the time because the images were hosed.
  7. Then I did a docker container ls -a to see which images were hosed. I did a series of docker container rm and docker image rm commands for any containers that were failing to start with those bizarre “/var/” errors.
  8. Then I repeated steps 4-8 until all of my apps were starting up.
  9. In retrospect, I probably could have just skipped steps 5-8 and just used docker container prune to delete all my containers, then docker image rm all of my images, and reboot, letting Docker automatically re-download all necessary containers, but I wanted to be minimally invasive.