In the previous release I had notifications of both core and supervisor having an update available. I’m wondering if maybe they’ve changed things so that supervisor doesn’t auto update any more? The auto update is bad when you use HA for our home security system. Nothing worse than being out of town only to have HA die on you because of auto install.
Supervisor fails after auto-update to 2022.07.0 many times… now it event cant start on 2022.06.2.
I dont know whats wrong 
Docker updated to latest version.
[21:05:37] INFO: Setup udev backend inside container
[21:05:37] INFO: Update udev information
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-rc: info: service legacy-services successfully started
[21:05:37] INFO: Starting local supervisor watchdog...
22-07-07 21:05:39 INFO (MainThread) [supervisor.bootstrap] Use the old homeassistant repository for machine extraction
22-07-07 21:05:39 INFO (MainThread) [__main__] Initializing Supervisor setup
22-07-07 21:05:39 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
22-07-07 23:05:39 WARNING (MainThread) [supervisor.bootstrap] Missing SUPERVISOR_MACHINE environment variable. Fallback to deprecated extraction!
22-07-07 23:05:39 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: qemux86-64
22-07-07 23:05:39 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor homeassistant/amd64-hassio-supervisor with version 2022.06.2
22-07-07 23:05:39 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
22-07-07 23:05:39 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-07-07 23:05:39 INFO (MainThread) [__main__] Setting up Supervisor
22-07-07 23:05:39 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
22-07-07 23:05:39 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
22-07-07 23:05:39 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface io.hass.os
22-07-07 23:05:39 WARNING (MainThread) [supervisor.dbus.manager] Can't load dbus interface io.hass.os: The name io.hass.os was not provided by any .service files
22-07-07 23:05:39 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.systemd1
22-07-07 23:05:39 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.login1
22-07-07 23:05:39 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.hostname1
22-07-07 23:05:40 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.timedate1
22-07-07 23:05:40 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.NetworkManager
22-07-07 23:05:40 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface de.pengutronix.rauc
22-07-07 23:05:40 WARNING (MainThread) [supervisor.dbus.manager] Can't load dbus interface de.pengutronix.rauc: The name de.pengutronix.rauc was not provided by any .service files
22-07-07 23:05:40 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.resolve1
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.info] Updating local host information
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.services] Updating service information
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.network] Updating local network information
22-07-07 23:05:40 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp3s0 which does not exist or is disabled.
22-07-07 23:05:40 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
22-07-07 23:05:40 WARNING (MainThread) [supervisor.host.apparmor] AppArmor is not enabled on host
22-07-07 23:05:40 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-cli with version 2022.06.0
22-07-07 23:05:40 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
22-07-07 23:05:40 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning hassio_cli application
s6-rc: info: service legacy-services: stopping
[21:05:41] INFO: Watchdog restart after closing
s6-svwait: fatal: supervisor died
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
[21:05:41] INFO: Supervisor restart after closing
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
I have a supervised install and this latest supervisor killed my install too. I am on the latest docker 20.10.17, on a pure Debian system. I check every box for a supported system.
Anyway, when supervisor starts the log is spammed with this message:
s6-ipcserver-socketbinder: fatal: unable to create socket: Permission denied
Other hassio containers seem to start for a few minutes, then randomly restart, but when I use docker logs to get a log, it returns nothing. Anybody have a clue how to fix it?
I can start the Home Assistant container separately on the same system, and it starts up. But the supervisor manages the mariadb for the recorder, so I can’t get that going, not to mention the other add-ons.
I’m not sure for 100% what helps but what I did was stopped my plex and nextcloud containers, additionally pull directly 2022.07.0 supervisor from repo… and that helps. After two reboots and many supervisor restarts still working good.
1 Like
Hey, refer to this post+link inside. should sort you out.
Thanks, updating docker, manually pulling the latest supervisor and restarting the service did it for me:
sudo apt-get update
sudo apt-get upgrade
docker pull homeassistant/amd64-hassio-supervisor
sudo systemctl restart hassio-supervisor.service
1 Like
I confirm, valid too me with Supervisor 2022.07.0
Thanks for this, I had the same issue (apt-get didnt upgrade it) but following the steps in that link fixed it all up for me - cheers!
1 Like
Thanks, worked for me too!!
If anyone has my problem, it seems that apparmor kernel modules were not loading for some reason. I switched to an older kernel, reinstalled the latest kernel, and rebooted. It came back up after that.
Thank you, this worked for me. Not sure how the hell you figured it out based on the error messages but I’m glad you are way better at this than I am. 
Helped me to fix it… Tnx.
Hi @kevincw01 @bkprath @CentralCommand , I am pretty much facing the exact same problem and I am using HomeAssistant OS on RaspberryPi,
so no apt-get cmds that are applicable in the docker/containerized environment.
My docker version is 19.03 and current supervisor is, I think 2022.06.2,
I am hearing from some discussion by @GSzabados that this new supervisor would need docker version 20+ to install the 2022.07.0 supervisor. This seems like a deadlock to me… I
How can I manage to solve this then?
NOTE: I do have access to the files in HAssOS. Is there something ugly that can be done?
I am not sure if this would work tbh. Its easier to just reimage/restore. But perhaps?
docker stop hassio_supervisor
docker kill hassio_supervisor
docker rm --force hassio_supervisor
then
docker pull homeassistant/aarch64-hassio-supervisor:2022.06.2
or
ha supervisor upgrade --version 2022.06.2
But I still that will try to install 2022.07 and fail because of your docker version. reimage. Frankly, even if you did get the supervisor under control, you don’t know if the rest of your install is corrupted. You haven’t even got there yet.
1 Like
The folks on the discord advised me to update hass os from the local command line incrementally (6, then 7 and finally latest 8.x) with ha os update --version 6.0 . This didn’t work for me so they suggested downloading the latest hass os image and flashing it to my SSD.
This did work.
This issue (for users with hass os, not a custom supervisor docker on Linux) was likely caused because I was on an old hass os (v5.13). Many of us were not updating the OS because there were bootloader issues with rpi and USB 3 SSD after that version and we were afraid to upgrade. Luckily this update did not cause a bootloader issue for me and my system was already down so I was willing to take the risk since I had nothing to lose.
The reflash of the SSD wipes your config. Luck for me I have been using the samba backup addon to save nightly ha backups to my nas. After the SSD flash and I did the initial web login to ha, I restored my configuration from a backup by uploading the most recent backup file from nas. Initially hass didn’t recover but I tried a supervisor restart from the local command line and that fixed it.
2 Likes
Damn this sucked a little. My HASS was acting weird and supervisor was down so I rebooted my NUC and everything died. After googling, I found this thread and this didn’t work for me because I was on ubuntu 19.04 and docker 20 doesn’t support that -___-. So I had to manually update ubuntu to 20.04 and then running these fixed it for me. Thanks all!
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install docker-ce docker-ce-cli containerd.io -y
docker pull homeassistant/amd64-hassio-supervisor
sudo systemctl restart hassio-supervisor.service
hm okay now this is weird. Anyone seeing this? If I reboot my system, the supervisor doesn’t come up nicely and I have to sudo systemctl restart hassio-supervisor.service to get my home assistant URL to work.
I’m on Ubuntu docker on NUC, and I know its not supported
Why you would like to install 2022.06.2? That is the one which is causing the issue. 2022.07.0 has already the code to verify if CgVersion is set or not, and it does not error if the CgVersion is not set.
But if you are running HA OS, then I would follow @kevincw01’s suggestion to update the OS as it should have been done a long time ago.
@OkayTrain121, generally as going forward, you will need docker version 20+, but the main issue comes from supervisor 2022.06.2 where it errors if the CgVersion is not set. But 2022.07.0 has a check for CgVersion and if it is not set, then it will not error and fail.
3 Likes
Thanks for this update.
I just came from vacation to a dead HA and after some hopeless poking I have found your post which saved me for today.
I am still on docker 19.03 without easy update path (OS upgrade is on my TODO list for quite some time 
), so I tried going straight to 2022.07 and it works!
So simply deleting all present supervisor docker images and then
docker image pull homeassistant/armhf-hassio-supervisor
did the trick for me.
1 Like
This was the solution for me. Thanks a ton.