Supervisor upgrade problem

Installation
1

Hi Alot of times when I try to upgrade supervisor in my enviroment it fails. This is a example of the log.

20-05-06 12:15:21 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-05-06 12:36:08 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.109.4
20-05-06 12:36:08 INFO (SyncWorker_3) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.108.9 to homeassistant/qemux86-64-homeassistant:0.109.4
20-05-06 12:36:08 INFO (SyncWorker_3) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.109.4.
20-05-06 12:49:19 ERROR (SyncWorker_3) [supervisor.docker.interface] Can’t install homeassistant/qemux86-64-homeassistant:0.109.4 -> 404 Client Error: Not Found (“no such image: homeassistant/qemux86-64-homeassistant:0.109.4: No such image: homeassistant/qemux86-64-homeassistant:0.109.4”).
20-05-06 12:49:19 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails

Anyone got some idea what can cause this and how to solve it?

thx
HĂĄkan

2

Cause : insufficient disk space
Solution : make more disk space available

3

Hi, I was getting the same issue. Wasn’t disk space for me…this was something to do with the systemd-resolved.service not started in my Ubuntu instance. I fixed that and rebooted it, and then was able to upgrade.

1 Like
4

Don’t think it is a disk problem. System is running on a VM with 128Gig disk :=)… Some times its works if I Stop all addons make them not start if reboot it could work but this time it dose not.

5

Then you can login to the host (the host, not the ha container) and run

docker pull homeassistant/qemux86-64-homeassistant:0.109.4

Show what messages are displayed on the console.

6

you meen logon to HassOS and then run docker pull?

7

yes, that is the easiest way to troubleshoot the problem

8

I figured it out :). When running the docker command it seems as it actually had downloaded a part of the new image already. This could be some timeout issues if you have like me a slow ADSL.

image
image903Ă—436 7.68 KB

9

The easiest way to fix : limit max concurrent downloads to 1

On raspbian I used this, don’t know where it is on HassOS

nano /etc/docker/daemon.json

{
“max-concurrent-downloads”: 1
}

10

Thx for help. My bad here I usually create all vhdx files but in this case I downloaded so when taking a look at disk size it was only 7gig. Hasos handel the expansion of the disk glorious :). Thx again