Update fails for install on a generic Linux host


I am trying to update my Hass.IO install and running in to the following error after pressing the update button in Hass.IO pane.

19-11-25 19:01:38 INFO (MainThread) [hassio.updater] Fetch update data from https://version.home-assistant.io/stable.json
19-11-25 19:08:18 INFO (MainThread) [hassio.host.info] Update local host information
19-11-25 19:08:18 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-11-25 19:08:19 INFO (MainThread) [hassio.host.services] Update service information
19-11-25 19:08:19 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-11-25 19:08:19 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-11-25 19:08:19 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
19-11-25 19:14:13 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.102.2
19-11-25 19:14:13 INFO (SyncWorker_16) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.101.2 to homeassistant/raspberrypi3-homeassistant:0.102.2
19-11-25 19:14:13 INFO (SyncWorker_16) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.102.2.
19-11-25 19:15:04 ERROR (SyncWorker_16) [hassio.docker.interface] Can't install homeassistant/raspberrypi3-homeassistant:0.102.2 -> 404 Client Error: Not Found ("no such image: homeassistant/raspberrypi3-homeassistant:0.102.2: No such image: homeassistant/raspberrypi3-homeassistant:0.102.2").
19-11-25 19:15:04 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails

I notice this error earlier in the log but, haven’t found much to show what this means…

19-11-25 16:59:25 WARNING (MainThread) [hassio.dbus.rauc] Host has no rauc support. OTA updates have been disabled.

I am using a Raspberry Pi 3 with Buster as the host and supervisor version 192.


I noticed that trying to manually pull the image appears to fail too…

devanl@HassPi3:~ $ docker pull homeassistant/raspberrypi3-homeassistant
Using default tag: latest
latest: Pulling from homeassistant/raspberrypi3-homeassistant
33b18ff7f9b7: Already exists
1f4eba7913e4: Already exists
4b7876757797: Already exists
025d5ca8b1d3: Already exists
f4085647b184: Already exists
ba7f8a38f0e4: Already exists
b2e5de686b38: Already exists
63e3f6d3be64: Already exists
b47de80f44d0: Already exists
803529260f21: Already exists
3a9122242f39: Already exists
403538b6b17b: Already exists
5baaaaa75e10: Already exists
a538d4ee7dc7: Already exists
f629db3e8592: Already exists
888b0e3aa4ca: Extracting [==================================================>]     266B/266B
88920fc2d5b3: Download complete
7ed05956e800: Download complete
1c18622079d2: Download complete
0b8407eb6248: Download complete
d81f9cc98008: Download complete
65ba6f946a7e: Download complete
119825fff10f: Download complete
failed to register layer: error creating overlay mount to /var/lib/docker/overlay2/49d9525b2de022b525e77edbed661be53911693d0c0c2f7d08b4936d206fdcd1/merged: too many levels of symbolic links

I have the same problem using Ubuntu 18.04 in a Virtualbox environment on a Window server 16, did you manage to solve this?

I ended up reinstalling and telling docket to use ‘overlay’ instead of ‘overlay2’.

From what I’ve read this probably wouldn’t do you much good.