Check your DNS settings.
This is what I see with ha dns info
~ $ ha dns info
host: 172.30.32.3
locals:
- dns://8.8.8.8
- dns://1.1.1.1
- dns://192.168.0.210
servers:
- dns://192.168.0.200
update_available: false
version: 2021.06.0
version_latest: 2021.06.0
192.168.0.210 is my pihole server, and i just added the server 0.200 (my router) plus the other two to give options and did a restart. Still the same error immediately…
And if I ping ghcr.io it seems to be resolving and working:
~ $ ping ghcr.io
PING ghcr.io (140.82.121.33): 56 data bytes
64 bytes from 140.82.121.33: seq=0 ttl=55 time=19.168 ms
64 bytes from 140.82.121.33: seq=1 ttl=55 time=17.859 ms
64 bytes from 140.82.121.33: seq=2 ttl=55 time=18.202 ms
64 bytes from 140.82.121.33: seq=3 ttl=55 time=17.752 ms
64 bytes from 140.82.121.33: seq=4 ttl=55 time=18.668 ms
^C
--- ghcr.io ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 17.752/18.329/19.168 ms
Also just checked a couple of repos in HACS, and can install stuff from there.
I also confirmed on the PiHole, and the ghcr.io is a permitted site there (and indeed HA seems to be the main thing going through there):
Still enough diskspace ?
37% used, 17 GB free…
and if you do in a ssh shell
ha supervisor update --version 2021.8.1
Same error:
~ $ ha supervisor update --version 2021.8.1
Processing... Done.
Error: Update of Supervisor failed: Can't install ghcr.io/home-assistant/armv7-hassio-supervisor:2021.08.1: 500 Server Error for http+docker://localhost/v1.41/images/createtag=2021.08.1&fromImage=ghcr.io%2Fhome-assistant%2Farmv7-hassio-supervisor: Internal Server Error ("Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: no such host")
I don’t know if it will work if you run HA OS, but maybe first :
docker pull homeassistant/armv7-hassio-supervisor:2021.08.1
If I add the DNS entry specifically into PiHole as a local address, it ends up with a 404 error instead
~ $ ha supervisor update --version 2021.8.1
Processing... Done.
Error: Update of Supervisor failed: Can't install ghcr.io/home-assistant/armv7-hassio-supervisor:2021.08.1: 404 Client Error for http+docker://localhost/v1.41/images/ghcr.io/home-assistant/armv7-hassio-supervisor:2021.08.1/json: Not Found ("no such image: ghcr.io/home-assistant/armv7-hassio-supervisor:2021.08.1: No such image: ghcr.io/home-assistant/armv7-hassio-supervisor:2021.08.1")
Nope, doesn’t work:
~ $ docker pull homeassistant/armv7-hassio-supervisor:2021.08.1
-bash: docker: command not found
But if I do ’ wget Package armv7-hassio-supervisor · GitHub’ , that works and downloads a file…
But it won’t probably put it in the correct place.
For docker pull to work you will need access to the host
I was meaning more that the file does actually exist and I can access it from the server, although I had to remove a : from the end of what was in the error message for it to work.
That SSH looks a bit complicated - will look at it after dinner. I’m wondering though if a backup and reinstall might be an easier route.
Just tried it, and I can’t get it to work. The server (HASS Pi) refuses the key.
That’s with a NTFS formatted USB stick with keys made with Puttygen, and the file authorized_keys formatted as ANSI and unix LF using Notepad++ containing the public key (with the private key used with port 22222 in Putty to access).
hassio su repair
Thank - tried but again it didn’t help.
The error message is saying that the image isn’t found, so I’m wondering if the issue is local to my device (although I can wget the same url fine, albeit to the wrong place).
1 Like
Took the SD card out to make a back-up image of it, and it’s now been about 15-20 minutes in starting up. So if it does dein to come back then I’ll give that a go, or if not I’ll burn a new one and restore from backup…
Edited to add - rebooted with a monitor connected, there’s a fail for the kernel time sync but aside from that it gets to the ha> prompt. But whilst i can connect to the observer on port 4357, I can’t connect to the dashboard on port 8123 nor SSH in.
I’m getting the feeling it’s time to cut my losses and do a new card and restore things if I can from yesterday’s backup.
Well it didn’t come back up, so I burned a new card and restored yesterday’s backup.
So I have no idea quite what happened to the original, but the new one is now up and running again on Supervisor 08.1 and all is working. Only glitch is a corrupted database, but I can live with that…
But thanks to everyone who chipped in with ideas to try and help with the problem, especially to @francisp
1 Like
I’m having the exact same issue with supervisor not updating, though in a VM on Proxmox instead of an RPi.
I even had it crash so hard I had to run a supervisor repair in order to get it to come back up at all.
I’ll give backing it up and reinstalling, then restoring the back up a shot if no one has any new ideas…
What is the best way to restore a backup if I can’t inject it directly into the FS?
A lot of people suggested that this is a DNS related issue, which is correct a lot of times.
However this is points to a DNS issue related to Docker and not Home Assistant necessarily. So depending on your setup, you might need to change DNS settings in your OS.
For me this happened after changing my network settings from DHCP to a static IP address, and I forgotten to manually enter the DNS server in Debian.