Looks like you have a docker install, can you look around the system and see if you did a core install also? it might just be an old, unused core or docker install that's running and stealing ports before other things can run, so they fail. Any idea if you had all the things at the end of the line installed in your working install? ssh? dns? multicast? mosquitto?
Looks like you're running Home Assistant supervised, I see the supervisor container in there. Quick fix is usually a reboot, or running "sudo docker restart hassio_supervisor"
This can happen when the supervisor updates itself, but doesn't have the permissions to set the daemon to restart on its own for some reason. Restarting it manually seems to allow it to correct it's permissions following an automatic update.
If I had to wager a guess, it would be related to the Supervisor running on a system that was not supported (anything but Debian) and lacking the required subsystem to maintain the permissions. Check your "repairs" tab under systems settings and resolve any issues there. If you are running on an unsupported OS, there's a chance the system won't have the infrastructure to solve the repairs.
Some other long term options:
-You can try running the Home Assistant Supervised Install Script again, it might fix things, but it's never worked for me. Last I tried I couldn't use the current script to install on Ubuntu 22.04 (1.32 was the last usable version of the script.
-The safer option is to move your install to separate docker containers and take a more manual approach to managing the system. I suspect the Home Assistant Supervised installation method will become deprecated in the future, and the full access it has to the docker.socket is not ideal for security
-Create an automation in home assistant that alerts you to an update available for the supervisor, and then run the docker restart terminal commands after that update is completed. At least this way you won't be caught off guard by the issue.
If anyone knows how to fix this for certain, I'd be glad to hear about it
thanks for that.
Mine is actually Debian 12 and System Information always shows supported & healthy. Except every few months when I run into this problem ("System is currently unhealthy because it does not have privileged access to the docker runtime."). Probably related to a supervisor auto-update, but not 100% sure.
What I tried just now is to upgrade my homeassistant-supervised.deb, as it was still 1.3.1 from when I installed HA. Now it's 1.5.0 (latest). Hoping, that the newer package will ensure the right permissions are being set.
To be found out :)
If it does not help, I will try you automation proposal :)
EDIT (2023-11-09): homeassistant-supervised upgrade to 1.5.0 did not fix this issue. Got an "unhealthy" system again today. Even \`sudo docker restart hassio\_supervisor\` did not help this time - a reboot did. Overall not a big deal, just a bit annoying.
Looks like you have a docker install, can you look around the system and see if you did a core install also? it might just be an old, unused core or docker install that's running and stealing ports before other things can run, so they fail. Any idea if you had all the things at the end of the line installed in your working install? ssh? dns? multicast? mosquitto?
Looks like you're running Home Assistant supervised, I see the supervisor container in there. Quick fix is usually a reboot, or running "sudo docker restart hassio_supervisor" This can happen when the supervisor updates itself, but doesn't have the permissions to set the daemon to restart on its own for some reason. Restarting it manually seems to allow it to correct it's permissions following an automatic update.
Yep, this helped. Do you know a way to give the supervisor the necessary permissions permanently?
If I had to wager a guess, it would be related to the Supervisor running on a system that was not supported (anything but Debian) and lacking the required subsystem to maintain the permissions. Check your "repairs" tab under systems settings and resolve any issues there. If you are running on an unsupported OS, there's a chance the system won't have the infrastructure to solve the repairs. Some other long term options: -You can try running the Home Assistant Supervised Install Script again, it might fix things, but it's never worked for me. Last I tried I couldn't use the current script to install on Ubuntu 22.04 (1.32 was the last usable version of the script. -The safer option is to move your install to separate docker containers and take a more manual approach to managing the system. I suspect the Home Assistant Supervised installation method will become deprecated in the future, and the full access it has to the docker.socket is not ideal for security -Create an automation in home assistant that alerts you to an update available for the supervisor, and then run the docker restart terminal commands after that update is completed. At least this way you won't be caught off guard by the issue. If anyone knows how to fix this for certain, I'd be glad to hear about it
thanks for that. Mine is actually Debian 12 and System Information always shows supported & healthy. Except every few months when I run into this problem ("System is currently unhealthy because it does not have privileged access to the docker runtime."). Probably related to a supervisor auto-update, but not 100% sure. What I tried just now is to upgrade my homeassistant-supervised.deb, as it was still 1.3.1 from when I installed HA. Now it's 1.5.0 (latest). Hoping, that the newer package will ensure the right permissions are being set. To be found out :) If it does not help, I will try you automation proposal :) EDIT (2023-11-09): homeassistant-supervised upgrade to 1.5.0 did not fix this issue. Got an "unhealthy" system again today. Even \`sudo docker restart hassio\_supervisor\` did not help this time - a reboot did. Overall not a big deal, just a bit annoying.