Latest Supervisor wont start

My supervisor also died this morning after I did a configuration adjustment and had to restart HA. I run HA supervised on a Debian 10 VM on Proxmox because I use a multihomed network and need the MQTT server accessible on other VLANs (there is probably a new / better solution, but I’ve been running this setup for several years now and I am reluctant to change it). Rebooting the VM did not help, supervisor kept restarting every 5 seconds with “CGroup” error.

Upgrading docker to 20.10.17 solved it (was on 19.03.8 previously, did apt update / upgrade, but had to manually upgrade the docker-ce package that “had been kept back”).

I looks like I was running supervisor version “supervisor-2022.06.dev3004” somehow - I usually turn all automatic updates off exactly because of situations like this, but I suppose the supervisor uses an independent setting; now it is asking me to update to version “supervisor-2022.06.2”. Did a development version of the supervisor accidentally reach the production channel?

looks like during my docker upgrade something happened because the docker has been updated but after reboot, there are no dockers. As I checked all containers exist with images… but the question is how to start all dockers? Is it any script for that?

Reboot host

@konradwalsh I tried 3 times.

No. The version history for stable channel can be found here if you want to check: History for stable.json - home-assistant/version · GitHub

Maybe you used latest at some point?

1 Like

@dmarczydlo I know very little about docker, but I guess you can try docker start hassio_supervisor

Ah, I think when trying to debug / solve the problem I did a docker pull hassio_supervisor.

1 Like

to start all docker containers, use the command:

docker restart $(docker ps -a -q)

1 Like

Unfortunately restarting the host does not always work to restart all docker containers.
and no pre-existing scripts that i know of.

But if you want you can try this on a linux machine:
for x in $(docker ps -a |grep -e 'homeassistant\|home-assistant' |awk '{print $1}'); do docker start $x; done

NOTE: still will start almost all containers related to HA Core/Supervisor and addons
and there is nothing dangerous in the command above.

Thank you. My case was a bit different. I had a custom docker configuration. The root dir was changed in past. After the upgrade, the new version wanted to be based on the default one. That was an issue.
I updated the configuration again and the for x in $(docker ps -a |grep -e 'homeassistant\|home-assistant' |awk '{print $1}'); do docker start $x; done runned all dockers :slight_smile: ah… night has been saved.

2 Likes

I am having a similar issue as above, using Home Assistant Operating System on a raspberry pi 3. I cannot update the docker version since the entire / directory is readonly. What is the process for updating docker, or getting the supervisor to run again (I tried manually pulling, and triggering the /usr/sbin/hassos-supervisor to no avail).

1 Like

What version of Home Assistant OS are you running on?

Version 5.12 (Raspberry Pi 3)

… joy… I knew these automatic supervisor updates would come to bite me in the rear… Off to try and fix it

Another one affected with raspbian :(. Trying to update docker to 20.10.17, but seems that Raspbian buster does not support is 19.03.13 :dizzy_face:

Fixed. Rasbpian buster test distribution contains 20.10.17. Just updated the sources, upgraded docker and rebooted. All working fine.

I dont have HAOS to test with, but do you have any admin/sudo credentials? to run the commands described here: Latest Supervisor wont start - #45 by NEoKhajitt

If it’s only docker that needs to be upgraded, you don’t have to make any changes in any directory.

PS: and welcome to the HA community :slight_smile:

Another one dead at 5am, revived after docker upgrade. Thanks, all.

I’m running HAOS in vmware ESXi on an Intel NUC. Same issue as others - can’t get the supervisor to start. Looks like i’m running an older version of docker (19.x). How do I update the docker version when running HAOS?

1 Like

I was also facing a sudden issue on this topic as well.

I am running hassio on linux mint , and in /etc/os-release,
NAME=“Linux Mint”
VERSION=“18.3 (Sylvia)”
VERSION_CODENAME=sylvia
UBUNTU_CODENAME=xenial

and wasn’t able to update since it says v19 of docker is up to date.

Referring to,

got docker updated to 20.10.7 and supervisor is up again.

Thank you guys.
I was starting to think if my SSD disk is failing to function correctly.

1 Like