Freshly installed Hass.io, Addons not possible to download

Configuration
1

After my last SD card broke, I just bought a new one and set up Hass.io on it. First thing I want to install after setup is adding the SSH addon.

However, whichever addon I try to add, I get the following error:

19-08-12 21:23:10 INFO (SyncWorker_2) [hassio.docker.interface] Pull image homeassistant/armv7-addon-ssh tag 6.1.
19-08-12 21:23:10 ERROR (SyncWorker_2) [hassio.docker.interface] Can't install homeassistant/armv7-addon-ssh:6.1 -> 500 Server Error: Internal Server Error ("Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:41917->[::1]:53: read: connection refused").

I have logged into the host OS to check that settings are allright, and everything works fine. I can ping internet without issues.

Anyone know what to do?

2

Things might be ok on the host, but not in the hass.io Docker container. One option would be to install Portainer on the host (in it’s own container). Then in the Portainer web interface you can connect to the hass.io container to try connectivity there.

I had a similar problem where my host was also running a DNS server (Dockerised pihole). Other containers on the same host couldn’t do DNS lookups, so nothing much worked. I had to run those containers with --dns=127.0.0.1 (or similar).

3

Thanks @michaelblight

Seems like it was a DNS issue, however, I now get another weird error…

19-08-13 16:28:06 INFO (MainThread) [hassio.addons] Create Home Assistant add-on data folder /data/addons/data/core_deconz
19-08-13 16:28:06 INFO (SyncWorker_12) [hassio.docker.interface] Pull image homeassistant/armhf-addon-deconz tag 3.1.
19-08-13 16:29:08 ERROR (SyncWorker_12) [hassio.docker.interface] Can't install homeassistant/armhf-addon-deconz:3.1 -> 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument").

Any ideas?

4

same problem here, I would be interested in a solution

5

I had the same issue. Taking the hint from Ronnie, I checked to see if it was a network issue and was surprised when I couldn’t resolve outside addresses. Home Assistant was using my router as a DNS server (which should have worked), however, I changed it to use Google’s DNS instead (8.8.8.8) and that fixed it.

I changed it by editing the /etc/resolv.conf file but it’s likely that I’ll have to do it again as Network Manager will probably overwrite it unless I use nmcli.

Using nmcli:
nmcli con edit “HassOS default”
set ipv4.dns 8.8.8.8
save
quit

2 Likes
6

this did work for me - I just replaced 127.0.0.11 with 8.8.8.8 in /etc/resolv.conf and restarted the box.

7

Thanks @corbeaux
I do same but via cli and I set IP address of my router

ha dns options --servers dns://IP_ADDRESS
ha dns restart