Problems updating HASS.IO Add-Ons with Docker

Tags: #<Tag:0x00007f739e2e4348>

I can’t update some Add-Ons using the HASS.IO tab’s Add-On Store and Dashboard.

I get the following after hitting the update button for Let’s Encrypt and for Samba Share. Other Add-Ons updated fine using their update buttons.

System log (tab: https://mysetup.duckdns.org/hassio/system)

18-04-12 08:17:05 INFO (MainThread) [hassio.core] Hass.io is up and running
18-04-12 08:19:37 INFO (SyncWorker_19) [hassio.docker.interface] Update docker 2.0 with homeassistant/armhf-addon-samba:3.0
18-04-12 08:19:37 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/armhf-addon-samba tag 3.0.
18-04-12 08:19:41 ERROR (SyncWorker_19) [hassio.docker.interface] Can't install homeassistant/armhf-addon-samba:3.0 -> 404 Client Error: Not Found ("no such image: homeassistant/armhf-addon-samba:3.0: No such image: homeassistant/armhf-addon-samba:3.0").
18-04-12 08:20:11 INFO (SyncWorker_14) [hassio.docker.interface] Update docker 1.2 with homeassistant/armhf-addon-letsencrypt:2.2
18-04-12 08:20:11 INFO (SyncWorker_14) [hassio.docker.interface] Pull image homeassistant/armhf-addon-letsencrypt tag 2.2.
18-04-12 08:20:15 ERROR (SyncWorker_14) [hassio.docker.interface] Can't install homeassistant/armhf-addon-letsencrypt:2.2 -> 404 Client Error: Not Found ("no such image: homeassistant/armhf-addon-letsencrypt:2.2: No such image: homeassistant/armhf-addon-letsencrypt:2.2").

I checked using PuTTY and have enough space on my hass.io pi:

core-ssh:~# df -h
Filesystem                Size      Used Available Use% Mounted on
none                      6.5G      2.6G      3.5G  43% /
tmpfs                   486.1M     64.0K    486.0M   0% /dev
tmpfs                   486.1M         0    486.1M   0% /sys/fs/cgroup
/dev/mmcblk0p3          294.1M    216.8M     61.8M  78% /dev/init
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /addons
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /backup
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /share
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /data
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /config
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /ssl
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /etc/resolv.conf
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /etc/hostname
/dev/mmcblk0p6            6.5G      2.6G      3.5G  43% /etc/hosts
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                   486.1M     64.0K    486.0M   0% /proc/timer_list
tmpfs                   486.1M     64.0K    486.0M   0% /proc/timer_stats
tmpfs                   486.1M     64.0K    486.0M   0% /proc/sched_debug
tmpfs                   486.1M         0    486.1M   0% /sys/firmware


More info in case it’s pertinent
I just let my Let’s Encrypt security key run out, then renewed it again, then updated to 0.66.1. I refreshed my internet browser’s cache several times, but my browser still warns me that my hass.io website is “Not Secure” in the address bar (even though it shows a valid security certificate).


I figure my browser will figure out the site is secure soon (I’m not too worried about this, just throwing the image in for clarification).

Several reboots of my Pi haven’t done anything. I updated my host system to resinos (GNU/Linux) 1.3. Anybody seen this before? I’ll wait and try this again.

Clean the browser cache

I thought that too, but tried that before posting. Cleaning the browser cache doesn’t work. My phone gets the same docker errors. Thanks for taking a stab at it though


Updates: Clearing my browser cache had no effect, but after 12hr my address bar lists my https://________.duckdns.org/ address as “Secure” again. So this was a red herring.

Still having the problem with Docker not updating Samba Share nor Let’s Encrypt to latest versions of their software. Strange

Just wanting to bump this thread. I’m running 0.67.1 and still getting these errors when trying to update via docker. I tried to uninstall sambashare and re-install, and docker still can’t find the sambashare 3.0 install package. Is there a way to manually pull a docker app using command line?

18-04-26 04:12:35 INFO (SyncWorker_19) [hassio.docker.interface] Update docker 2.0 with homeassistant/armhf-addon-samba:3.0
18-04-26 04:12:35 INFO (SyncWorker_19) [hassio.docker.interface] Pull image homeassistant/armhf-addon-samba tag 3.0.
18-04-26 04:12:40 ERROR (SyncWorker_19) [hassio.docker.interface] Can't install homeassistant/armhf-addon-samba:3.0 -> 404 Client Error: Not Found ("no such image: homeassistant/armhf-addon-samba:3.0: No such image: homeassistant/armhf-addon-samba:3.0").
18-04-26 04:17:22 INFO (SyncWorker_1) [hassio.docker.interface] Stop homeassistant/armhf-addon-samba docker application
18-04-26 04:17:23 INFO (SyncWorker_1) [hassio.docker.interface] Clean homeassistant/armhf-addon-samba docker application
18-04-26 04:17:23 INFO (SyncWorker_1) [hassio.docker.interface] Remove docker homeassistant/armhf-addon-samba with latest and 2.0
18-04-26 04:17:23 INFO (MainThread) [hassio.addons.addon] Remove Home-Assistant addon data folder /data/addons/data/core_samba
18-04-26 04:17:33 INFO (MainThread) [hassio.addons.addon] Create Home-Assistant addon data folder /data/addons/data/core_samba
18-04-26 04:17:33 INFO (SyncWorker_15) [hassio.docker.interface] Pull image homeassistant/armhf-addon-samba tag 3.0.
18-04-26 04:17:44 ERROR (SyncWorker_15) [hassio.docker.interface] Can't install homeassistant/armhf-addon-samba:3.0 -> 404 Client Error: Not Found ("no such image: homeassistant/armhf-addon-samba:3.0: No such image: homeassistant/armhf-addon-samba:3.0")

Update: I SSH’d into the root of my homeassistant setup

  • By generating a RSA-SSH key (in Cygwin actually, then importing into puttygen) and copying the “Public key for pasting into OpenSSH authorized_keys file:” field into the authorized_keys file in my Pi’s SD card’s root directory (DO NOT REFORMAT ANY PARTITIONS IF WINDOWS ASKS YOU TO).
  • I added the private key (also imported from Cygwin private key via PuTTYgen) to PuTTY under “Connection > SSH > auth > Private key for authentication”
  • Then I connected with PuTTY

Here’s what my log is showing now after manually trying to pull the docker images for samba share and let’s encrypt. I previously uninstalled samba share, which is why it doesn’t show up in my list of images. Both samba share and let’s encrypt are older versions on my system.

docker pull homeassistant/armhf-addon-samba:latest

[email protected]:~# docker images
REPOSITORY                                 TAG                 IMAGE ID            CREATED             SIZE
homeassistant/raspberrypi3-homeassistant   0.67.1              57374809c1c4        11 days ago         1.02GB
homeassistant/raspberrypi3-homeassistant   latest              57374809c1c4        11 days ago         1.02GB
homeassistant/armhf-hassio-supervisor      0.101               512f3c9a457e        2 weeks ago         122MB
homeassistant/armhf-hassio-supervisor      latest              512f3c9a457e        2 weeks ago         122MB
homeassistant/armhf-addon-duckdns          1.3                 b308b1e8c494        4 weeks ago         18.9MB
homeassistant/armhf-addon-duckdns          latest              b308b1e8c494        4 weeks ago         18.9MB
homeassistant/resinos-hassio               1.3-raspberrypi3    ac4f51d200ff        7 weeks ago         244MB
homeassistant/armhf-addon-ssh              3.4                 03bfae73187c        2 months ago        71MB
homeassistant/armhf-addon-ssh              latest              03bfae73187c        2 months ago        71MB
homeassistant/armhf-addon-rpc_shutdown     0.3                 ad26a83bbbf5        6 months ago        41.3MB
homeassistant/armhf-addon-rpc_shutdown     latest              ad26a83bbbf5        6 months ago        41.3MB
homeassistant/armhf-addon-letsencrypt      1.2                 863cdeccb471        9 months ago        72.3MB
homeassistant/armhf-addon-letsencrypt      latest              863cdeccb471        9 months ago        72.3MB
homeassistant/armhf-addon-mosquitto        1.0                 b6d3ba2c0d20        9 months ago        14.6MB
homeassistant/armhf-addon-mosquitto        latest              b6d3ba2c0d20        9 months ago        14.6MB
vkorn/armhf-ps4waker                       0.0.2               8e00a799120c        10 months ago       64.6MB
vkorn/armhf-ps4waker                       latest              8e00a799120c        10 months ago       64.6MB

[email protected]:~# docker ps
CONTAINER ID        IMAGE                                      COMMAND                  CREATED             STATUS              PORTS                                            NAMES
9b03a0f78e15        vkorn/armhf-ps4waker                       "/usr/bin/entry.sh..."   11 minutes ago      Up 11 minutes                                                        addon_e5829d31_ps4waker
4767799d8262        homeassistant/raspberrypi3-homeassistant   "/usr/bin/entry.sh..."   12 minutes ago      Up 12 minutes                                                        homeassistant
4bd8a665b163        homeassistant/armhf-addon-duckdns          "/usr/bin/entry.sh..."   12 minutes ago      Up 12 minutes                                                        addon_core_duckdns
6b7bf6db836e        homeassistant/armhf-addon-ssh              "/usr/bin/entry.sh..."   12 minutes ago      Up 12 minutes       0.0.0.0:22->22/tcp                               addon_core_ssh
b491c23ce2c0        homeassistant/armhf-addon-rpc_shutdown     "/usr/bin/entry.sh..."   12 minutes ago      Up 12 minutes                                                        addon_core_rpc_shutdown
1191da06437a        homeassistant/armhf-addon-mosquitto        "/usr/bin/entry.sh..."   14 minutes ago      Up 14 minutes       0.0.0.0:1883->1883/tcp, 0.0.0.0:8883->8883/tcp   addon_core_mosquitto
23473138bc9c        homeassistant/armhf-hassio-supervisor      "/usr/bin/entry.sh..."   2 weeks ago         Up 15 minutes                                                        resin_supervisor

[email protected]:~# docker pull homeassistant/armhf-addon-samba:3.0
3.0: Pulling from homeassistant/armhf-addon-samba
95d54dd4bdad: Already exists
72bf7d76c392: Already exists
0da33bb3490c: Already exists
a8ece121d40c: Already exists
308601741197: Already exists
e22c64886831: Extracting [==================================================>]  11.44MB/11.44MB
919bd02cb95e: Ready to download
830e5d54a26b: Ready to download
d4e12538e0b5: Ready to download
failed to register layer: open /var/lib/docker/aufs/layers/861f3ea040dcb36042ef8a9d3ee54705b4a4b6f9ecf91713e7f2a7f2d4020d94: no such file or directory

[email protected]:~# docker pull homeassistant/armhf-addon-letsencrypt:latest
latest: Pulling from homeassistant/armhf-addon-letsencrypt
95d54dd4bdad: Already exists
72bf7d76c392: Already exists
0da33bb3490c: Already exists
a8ece121d40c: Already exists
308601741197: Already exists
ffb787184911: Extracting [==================================================>]   18.3MB/18.3MB
1e7fe51848c8: Ready to download
3eaa0b1d9b15: Ready to download
failed to register layer: open /var/lib/docker/aufs/layers/861f3ea040dcb36042ef8a9d3ee54705b4a4b6f9ecf91713e7f2a7f2d4020d94: no such file or directory
[email protected]:~#

Update: This github post says that the failed to register layer: open /var/lib/docker/aufs/layers/ problem is a known bug with Docker, which happens almost randomly, and suggested that the only way to fix it was “manually removing /var/lib/docker.” But I realized that all of HomeAssistant’s data is located inside /var/lib/docker.

In hindsight, I should have just gone to my snapshots page in HASS.IO and done a “Wipe & Restore” from my most recent snapshot. That should fix the problem.

But read on if you’re curious …or dumb like I was, lol… :stuck_out_tongue:


Instead of doing a Wipe & Restore of my installation from my HASS.IO snapshot, I did the following procedures to attempt (unsuccessfully) to fix Docker. I later realized I couldn’t fix Docker, so backed up my Pi SD card and re-installed HASS.IO from scratch:

Before anything, I backed up my HASS.IO install by making a snapshot.

Then I gained root access to my Pi (see the above post for how to do that). Then I tried to follow the github poster’s instructions for refreshing Docker from command-line by removing all images and packages and re-installing. This proved impossible without nuking HASS.IO, since HASS.IO itself is a Docker image:

[email protected]:~# docker stop $(docker ps -a -q)
730e3e1e2b90
9b03a0f78e15
4bd8a665b163
6b7bf6db836e
b491c23ce2c0
1191da06437a
23473138bc9c
[email protected]:~# docker rm $(docker ps -a -q)
730e3e1e2b90
9b03a0f78e15
4bd8a665b163
6b7bf6db836e
b491c23ce2c0
1191da06437a
Error response from daemon: You cannot remove a running container 23473138bc9c289d6c5d67e6e8abb62992b6f5100f5145940a8c00cb6c6448fb. Stop the container before attempting removal or force remove
[email protected]:~# docker ps
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS               NAMES
23473138bc9c        homeassistant/armhf-hassio-supervisor   "/usr/bin/entry.sh..."   2 weeks ago         Up 1 second                             resin_supervisor
[email protected]:~# docker stop 23473138bc9c289d6c5d67e6e8abb62992b6f5100f5145940a8c00cb6c6448fb
23473138bc9c289d6c5d67e6e8abb62992b6f5100f5145940a8c00cb6c6448fb
[email protected]:~# docker rm 23473138bc9c289d6c5d67e6e8abb62992b6f5100f5145940a8c00cb6c6448fb
23473138bc9c289d6c5d67e6e8abb62992b6f5100f5145940a8c00cb6c6448fb

[email protected]:~# docker rmi $(docker images -q)
Untagged: homeassistant/resinos-hassio:1.3-raspberrypi3
Untagged: homeassistant/[email protected]:ad6e69914a0d1b6c13a412c7393b4435752ba03174b4a9a7fd5aee7ab7b7627f
Deleted: sha256:ac4f51d200ffa3f2a8470d3241bf4ace42267b24ec36028c928155b3065417e8
Deleted: sha256:1a55c1dd95631cecf2167483e2b54e934a4d3f39ad187d4a3a8856c8ad7644c0
Error response from daemon: conflict: unable to delete 57374809c1c4 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 57374809c1c4 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 512f3c9a457e (cannot be forced) - image is being used by running container c7d26c040236
Error response from daemon: conflict: unable to delete 512f3c9a457e (cannot be forced) - image is being used by running container c7d26c040236
Error response from daemon: conflict: unable to delete b308b1e8c494 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete b308b1e8c494 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 03bfae73187c (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 03bfae73187c (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete ad26a83bbbf5 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete ad26a83bbbf5 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 863cdeccb471 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 863cdeccb471 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete b6d3ba2c0d20 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete b6d3ba2c0d20 (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 8e00a799120c (must be forced) - image is referenced in multiple repositories
Error response from daemon: conflict: unable to delete 8e00a799120c (must be forced) - image is referenced in multiple repositories
[email protected]:~# service docker stop #
-sh: service: command not found
[email protected]:~# service docker stop
-sh: service: command not found
[email protected]:~# rm -rf /var/lib/docker/overlay2

[email protected]:~# docker ps
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS               NAMES
c7d26c040236        homeassistant/armhf-hassio-supervisor   "/usr/bin/entry.sh..."   4 minutes ago       Up 3 minutes                            resin_supervisor
[email protected]:~# docker pull homeassistant/armhf-addon-samba:latest
latest: Pulling from homeassistant/armhf-addon-samba
95d54dd4bdad: Already exists
72bf7d76c392: Already exists
0da33bb3490c: Already exists
a8ece121d40c: Already exists
308601741197: Already exists
e22c64886831: Extracting [==================================================>]  11.44MB/11.44MB
919bd02cb95e: Ready to download
830e5d54a26b: Ready to download
d4e12538e0b5: Ready to download
failed to register layer: open /var/lib/docker/aufs/layers/861f3ea040dcb36042ef8a9d3ee54705b4a4b6f9ecf91713e7f2a7f2d4020d94: no such file or directory
[email protected]:~# service docker stop
-sh: service: command not found

[email protected]:~# docker system prune
WARNING! This will remove:
        - all stopped containers
        - all volumes not used by at least one container
        - all networks not used by at least one container
        - all dangling images
Are you sure you want to continue? [y/N] n

[email protected]:~# docker system prune
WARNING! This will remove:
        - all stopped containers
        - all volumes not used by at least one container
        - all networks not used by at least one container
        - all dangling images
Are you sure you want to continue? [y/N] y
error during connect: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.31/networks/prune: EOF

[email protected]:~# docker images
REPOSITORY                                 TAG                 IMAGE ID            CREATED             SIZE
homeassistant/raspberrypi3-homeassistant   0.67.1              57374809c1c4        11 days ago         1.02GB
homeassistant/raspberrypi3-homeassistant   latest              57374809c1c4        11 days ago         1.02GB
homeassistant/armhf-hassio-supervisor      0.101               512f3c9a457e        2 weeks ago         122MB
homeassistant/armhf-hassio-supervisor      latest              512f3c9a457e        2 weeks ago         122MB
homeassistant/armhf-addon-duckdns          1.3                 b308b1e8c494        4 weeks ago         18.9MB
homeassistant/armhf-addon-duckdns          latest              b308b1e8c494        4 weeks ago         18.9MB
homeassistant/armhf-addon-ssh              3.4                 03bfae73187c        2 months ago        71MB
homeassistant/armhf-addon-ssh              latest              03bfae73187c        2 months ago        71MB
homeassistant/armhf-addon-rpc_shutdown     0.3                 ad26a83bbbf5        6 months ago        41.3MB
homeassistant/armhf-addon-rpc_shutdown     latest              ad26a83bbbf5        6 months ago        41.3MB
homeassistant/armhf-addon-letsencrypt      1.2                 863cdeccb471        9 months ago        72.3MB
homeassistant/armhf-addon-letsencrypt      latest              863cdeccb471        9 months ago        72.3MB
homeassistant/armhf-addon-mosquitto        1.0                 b6d3ba2c0d20        9 months ago        14.6MB
homeassistant/armhf-addon-mosquitto        latest              b6d3ba2c0d20        9 months ago        14.6MB
vkorn/armhf-ps4waker                       0.0.2               8e00a799120c        10 months ago       64.6MB
vkorn/armhf-ps4waker                       latest              8e00a799120c        10 months ago       64.6MB
[email protected]:~# docker pull homeassistant/armhf-addon-samba:latest
latest: Pulling from homeassistant/armhf-addon-samba
95d54dd4bdad: Already exists
72bf7d76c392: Already exists
0da33bb3490c: Already exists
a8ece121d40c: Already exists
308601741197: Already exists
e22c64886831: Extracting [==================================================>]  11.44MB/11.44MB
919bd02cb95e: Ready to download
830e5d54a26b: Ready to download
d4e12538e0b5: Ready to download
failed to register layer: open /var/lib/docker/aufs/layers/861f3ea040dcb36042ef8a9d3ee54705b4a4b6f9ecf91713e7f2a7f2d4020d94: no such file or directory
[email protected]:~# cd var
-sh: cd: var: No such file or directory
[email protected]:~# ls
[email protected]:~# bash
[email protected]:~# docker ps
CONTAINER ID        IMAGE                                   COMMAND                  CREATED             STATUS              PORTS               NAMES
085c3209479c        homeassistant/armhf-hassio-supervisor   "/usr/bin/entry.sh..."   2 minutes ago       Up 2 minutes                            resin_supervisor
[email protected]:~#

Realizing I would have to re-install HASS.IO to truly “refresh” Docker manually, I backed up my SD Card onto my Windows PC. resin-boot (Drive D: in my case) is the only partition readable by Windows and does not contain HomeAssistant configuration data. I backed up my authorized_keys file from here.

I put my Pi SD card into my Windows PC and opened DiskInternals Linux Reader to read the Linux partitions on my Pi SD card attached to my Windows PC. I navigated to /var/lib/docker\resin-data\, saved my backup, share, ssl, and homeassistant folders.

Then I downloaded the HASS.IO install image, wiped my current Pi SD card by going to Windows\Control Panel\System and Security\Administrative Tools\Computer Management > Disk Management and deleting all volumes on my Pi’s SD card.

I used Win32DiskImager to write the HASS.IO install image onto my SD card. I then closed DiskInternals Linux Reader and re-opened it. I put the authorized_keys file back into resin-boot. I put the Pi SD card back into my Pi, turned on the Pi, waited a few minutes, found the IP of my Pi in my router’s “attached devices” list, logged in using HASSIO_IP_HERE:8123 (hassio.local:8123 didn’t work for me).

Once HASS.IO was running again, i installed Samba Share from the HASS.IO > Addons tab (thank Jesus, Samba finally installed correctly from Docker, lol), started Samba Share.

I then found my HASS.IO Pi on my LAN in Windows File Explorer (now that Samba Share was turned on), copied my latest backed-up HomeAssistant system “snapshot” from my Windows desktop to the “backup” folder on my Pi’s samba share.

I then logged into HASS.IO via Internet Explorer, installed that “snapshot” through HASS.IO (I didn’t choose to restore the faulty Let’s Encrypt - idk if that matters). Then installed, configured, and ran the Let’s Encrypt Addon. Then rebooted the Pi.

Interestingly, refreshing my install manually like this made my custom PS4 component not available anymore, but I think that will be an easy re-install.