500 Server Error

[Ali8904]

Hey i just noticed, the addon was not running anymore. When i tried to start it i got a 500 server error. Since i had similar errors in the past, i removed it and wanted it to install again. While i reinstalled the addon i got the same error message.

Since the last update was uploaded at 30. of januar, i mad a roll back to the last full backup of HA, only to find out, there was absolutely no addon included.

what could i do to get the addon back on my system?

ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/sabeechen/hassio-google-drive-backup-aarch64:0.112.1: 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/sabeechen/hassio-google-drive-backup-aarch64:0.112.1/json: Internal Server Error ("layer does not exist")

[massimoa01]

I experienced the same problem as Ali8904 and I followed exactly the say process of removing and reinstalling but the error is different: "Can't install ghcr.io/sabeechen/hassio-google-drive-backup-armv7:0.112.1: 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/sabeechen/hassio-google-drive-backup-armv7:0.112.1/json: Internal Server Error ("readlink /mnt/data/docker/overlay2: invalid argument")"

[massimoa01]

command "ha su repair" (suggested in other thread )seems to have solved the problem for me

[Ali8904]

It did indeed repair something, but to me it seems that it only did repair addons, which are installed. and unfortunately, i still cannoot install that addon

24-02-11 19:05:08 INFO (MainThread) [supervisor.addons.manager] Found 3 add-ons to repair
24-02-11 19:05:08 INFO (MainThread) [supervisor.addons.manager] Repairing for add-on: core_nginx_proxy
24-02-11 19:05:08 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-nginx_proxy with tag 3.8.0.
24-02-11 19:05:15 INFO (MainThread) [supervisor.addons.manager] Repairing for add-on: core_duckdns
24-02-11 19:05:15 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-duckdns with tag 1.15.0.
24-02-11 19:05:51 INFO (MainThread) [supervisor.addons.manager] Repairing for add-on: core_samba
24-02-11 19:05:51 INFO (MainThread) [supervisor.docker.interface] Downloading docker image homeassistant/aarch64-addon-samba with tag 12.3.0.
24-02-11 19:06:07 INFO (MainThread) [supervisor.supervisor] Repairing Supervisor 2024.01.1
24-02-11 19:06:07 INFO (MainThread) [supervisor.core] Finished repair of Supervisor Environment
24-02-11 19:06:55 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/sabeechen/hassio-google-drive-backup-aarch64 with tag 0.112.1.
24-02-11 19:06:58 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/sabeechen/hassio-google-drive-backup-aarch64:0.112.1: 500 Server Error for http+docker://localhost/v1.43/images/ghcr.io/sabeechen/hassio-google-drive-backup-aarch64:0.112.1/json: Internal Server Error ("layer does not exist")

[sabeechen]

I'm almost certain this another instance of Docker corruption, it can manifest as any number of docker errors. You can verify this by running the SSH Addon with protection mode disabled and seeing if the command:

docker pull ghcr.io/sabeechen/hassio-google-drive-backup-$(ha su info | grep arch | sed "s/arch: //"):0.112.1

Is able to run. Because Home Assistant's supervisor makes it difficult to get access to the host filesystem, the corruption is difficult to fix. I had one user who was able to fix it here by installing SSH keys to let you SSH into the host system, which is pretty annoying.

The issue is pretty well reported in the HA supervisor issues, but I'm not aware of work being done to fix the root cause. Its an issue that affects anything that runs on Home Assistant (not just this addon). Most solve it by reinstalling Home Assistant from scratch, unfortunately.

[Ali8904]

I dont have any programming or it backround. Idid try and let chat gpt explain what to do or was trying to understand what could help. bur i could not.

terminal will just give me "bash: docker: command not found".

Asked a friend he mentioned to go to root with cd/root and it did not work. . .