Started getting errors upgrading Addons

I’m running the latest Home Assistant 2022.3.5 on the Blue Odroid N2. I’ve been running this HA instance for almost 3 years now and have a fairly robust setup.

However, in the past week my Addon upgrades have started failing. Here’s the two errors I’ve received so far:


Can’t install esphome/esphome-hassio-aarch64:2022.3.0: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=2022.3.0&fromImage=esphome%2Fesphome-hassio-aarch64&platform=linux%2Farm64: Internal Server Error (“Head “https://registry-1.docker.io/v2/esphome/esphome-hassio-aarch64/manifests/2022.3.0”: Get “https://auth.docker.io/token?scope=repository%3Aesphome%2Fesphome-hassio-aarch64%3Apull&service=registry.docker.io”: unexpected EOF”)

The forum won’t let me post multiple links in a post since I’m new, so I’ll post the next in a reply.

I really don’t want to have to start a new install, but I have no idea what’s actually happening here or how to fix it. Any ideas out there?

Here’s the next error I encountered today:

Can’t install homeassistant/aarch64-addon-zwave_js:0.1.55: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=0.1.55&fromImage=homeassistant%2Faarch64-addon-zwave_js&platform=linux%2Farm64: Internal Server Error (“Head “https://registry-1.docker.io/v2/homeassistant/aarch64-addon-zwave_js/manifests/0.1.55”: Get “https://auth.docker.io/token?scope=repository%3Ahomeassistant%2Faarch64-addon-zwave_js%3Apull&service=registry.docker.io”: unexpected EOF”)

The two have the “unexpected EOF” in common, but I’m not sure what that means. Thoughts?

Are you low on disk space?

Interesting question… I’ve never thought about disk space when I’m running from an SD card or eMMC. I’ll go take a look.

Hmm. a “df-h” from within the SSH session shows /dev/mmcblk1p4 only having used 7.9G of an available 100.2G. tmpfs shows 0 used of 1.8G available.

Neither of those would seem to be the culprit - if disk space were the issue - but I also realize this is only inside the container running HA itself.

Would you happen to know if these images being downloaded are downloaded somewhere outside of the HA container? If so, I’ll have to go re-learn how to get into developer mode to see that.

Thanks @nickrout for your continued assistance!

Maybe some error in the building of aarch64 addons?

Managed to get port 22222 access to check disk space in Home Assistant OS and it looks like disk space is abundant there.

The aarch64 addons I’ve had issues trying to update so far are ESPHome and Z-Wave JS. If there were an issue with those, I’m guessing there would be many voices complaining, but I haven’t found anything else.

I may try loading up HA on another Raspberry PI or something, and then working backward through my backups to see if something went south recently. My Blue is on a UPS, but I guess something might have glitched at some point.

@nickrout - it makes sense that the EOF could be related to disk space, so I’ll keep trying to investigate here to see if I can understand better how the addons are pulled down and stored during an upgrade. Maybe I’m missing something that will become clear with a little more digging.

I loaded a new installation of HA on a Raspberry PI4 and imported backups, but all of my backups back to the beginning of February 2022 had the same issue. Looks like I may be starting over on a new install on another Odroid. I’m not seeing anyone else having this issue.

Have you posted an issue on gthub?

Thanks, Nick. No, I didn’t know that was an option.

Interestingly, I just upgraded to HA 2022.3.6, tried the install again, and it works. Now I don’t have a way to recreate it.

I’ll keep an eye on it, and if it happens again I’ll post to github.

Thanks for your help - both times!

I’m having this exact issue.

I’m on 2022.3.5, and have a Core update that won’t install.

I also get the same “Can’t install” message when I try to update or install new add-ons.

Core isn’t an addon.