supervisor: Supervisor 2022.11.1 wont install

Here is a one liner version of what Mike pasted above

version="2022.11.2" arch=`docker image ls | grep -- '-hassio-observer'  | awk '{print $1}' | awk -F/ '{print $3}' | awk -F- '{print $1}'` && docker pull "ghcr.io/home-assistant/${arch}-hassio-supervisor:${version}" && docker tag "ghcr.io/home-assistant/${arch}-hassio-supervisor:${version}" "ghcr.io/home-assistant/${arch}-hassio-supervisor:latest" && docker stop hassio_supervisor && docker rm hassio_supervisor

If you had the 2022.11.0 beta installed I had to do this to get mine to update:

docker exec -it hassio_supervisor /bin/bash
# pip3 install --upgrade dbus-fast
# exit
docker restart hassio_supervisor

Someone probably has a better way to do this so you might wait for a better fix as this one is a bit risky to do.

This kind of worked for me. Only had access to OS CLI (running in a VM). You can use docker commands by typing login. After the above commands my supervisor was back to ‘normal’, allowing me to update it to 2022.11.2. My core is back up but add-ons are having issues, running su repair as we speak since none of the images exist.

I have the same issue here, except it’s from Supervisor 2022.11.0 to 2022.11.2 and same issue updatng Core from 2022.10.4 to 2022.11.2. I am using HAOS in VIrtualBox. There doesn’t seem to be anything unusal in the logs I checked. Restart is not always possible. However I restarted from the Virtualbox (using ACPI shutdown then starting back up) and now I cannot take any backups because Creating a backup is not possible right now because the system is in startup state

Let me know if you need me to look somewhere for further information

That’s why I said the third option is a reinstall and then restore a backup. Reinstall will put you on the latest version of supervisor. At that point you should be able to restore everything else around supervisor without issue.

Just had some comments on this option, about people losing their entire history… Guess that is a serious reason to keep this option as last resort.

yeah it is updated I see now

@Mariusthvdb did you try to restore a backup on the current system? If so then that won’t work.

Backups don’t really include much from supervisor except the values of its current options. It will not revert to an older version of supervisor. Also since supervisor is the one doing the restoring it won’t work if supervisor doesn’t work.

That’s why I said the third option is a reinstall and then restore a backup. Reinstall will put you on the latest version of supervisor. At that point you should be able to restore everything else around supervisor without issue.

Hey Mike, I fear for the many users that will be confronted with this issue the next few hours, a more detailed an precise list of commands, probably in a community post, is required…

I mean, I can shell into a terminal, at port 22222, but am afraid need a bit more direction than

find the supervisor image name that looks like that in the list. Plug in the arch you use.

as will most HAOS users…

also, de we need to get back to the beta channel for Nicks commands, or can we also do that on stable.

also @tjorim

My core is back up but add-ons are having issues, running su repair as we speak since none of the images exist.

This ofc is a major issue, and personally I wont dare to issue the commands, since all of my system is depending on the add-ons (Zwave/Mqtt) to name but 2 fundamentals…

Unfortunately you’re going to need to do what bdraco suggested. Because of where this error occurs supervisor can’t update itself out of this. Attempting to update gets stuck indefinitely. The alternative solution is this:

arch="<INSERT ARCH HERE>"
docker pull "ghcr.io/home-assistant/${arch}-hassio-supervisor:2022.11.2"
docker tag "ghcr.io/home-assistant/${arch}-hassio-supervisor:2022.11.2" "ghcr.io/home-assistant/${arch}-hassio-supervisor:latest"
docker stop hassio_supervisor && docker rm hassio_supervisor

Note that you need to put your system arch in arch if you use this. If you don’t know then do a docker image ls and find the supervisor image name that looks like that in the list. Plug in the arch you use. Note that you can also find the value for arch in the response to ha supervisor info. Since the API seems unreliable in this state I figured I’d put an alternative that didn’t involve it but that is easier, just copy and paste the value from arch into <INSERT ARCH HERE>

After those steps are done you don’t have to start supervisor again. Observer will remake supervisor’s container on the new version and you’ll be past this.

This for reference is a general solution to this problem (I use essentially the same process any time I break my dev box with something 😄 ). Bdraco’s works fine but is a specific solution to the particular issue at hand.

If you had the 2022.11.0 beta installed I had to do this to get mine to update:

docker exec -it hassio_supervisor /bin/bash
pip3 install --upgrade dbus-fast
docker restart hassio_supervisor

Someone probably has a better way to do this so you might wait for a better fix as this one is a bit risky to do.

I lost access to HA and thus the terminal add-on after a restart, is there a way to get access to the docker command using the host CLI? Seems limited to ha >. Can’t manually stop/start/restart core, I see the landingpage with su logs.