supervisor: Error updating ESPHome: Can't install ghcr.io/esphome/esphome-hassio:2023.4.3
Describe the issue you are experiencing
Starting after the ESPHome 2023.3.2 release, updating of the Add-On stopped working. When I attempted to upgrade the ESPHome Add-on after ESPHome 2023.4.0 was released, it started returning an error. I am able to uninstall/reinstall the Add-on but updating always fails.
The error in the Hosts log leads me to believe it’s attempting to download a build for the wrong platform (ARMv6) and failing. I am at a loss on how to troubleshoot this further.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
-
Receive notification of Update available for ESPHome
-
Open Modal detailing update and click INSTALL
-
Receive error briefly at bottom of screen.
Anything in the Supervisor logs that might be useful for us?
23-05-03 14:34:05 INFO (SyncWorker_2) [supervisor.docker.interface] Cleanup images: ['ghcr.io/home-assistant/raspberrypi2-homeassistant:2023.4.6']
23-05-03 14:34:50 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug 7efd0127
23-05-03 14:34:50 INFO (MainThread) [supervisor.backups.manager] Backing up 7efd0127 store Add-ons
23-05-03 14:34:50 INFO (MainThread) [supervisor.addons.addon] Building backup for add-on 5c53de3b_esphome
23-05-03 14:34:50 INFO (MainThread) [supervisor.addons.addon] Finish backup for addon 5c53de3b_esphome
23-05-03 14:34:51 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug 7efd0127 completed
23-05-03 14:34:51 INFO (SyncWorker_0) [supervisor.docker.addon] Updating image ghcr.io/esphome/esphome-hassio:2023.4.2 to ghcr.io/esphome/esphome-hassio:2023.4.3
23-05-03 14:34:51 INFO (SyncWorker_0) [supervisor.docker.interface] Downloading docker image ghcr.io/esphome/esphome-hassio with tag 2023.4.3.
23-05-03 14:34:53 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install ghcr.io/esphome/esphome-hassio:2023.4.3: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.4.3/json: Not Found ("No such image: ghcr.io/esphome/esphome-hassio:2023.4.3")
System Health information
System Information
| version | core-2023.6.2 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.4 |
| os_name | Linux |
| os_version | 6.1.21-v7 |
| arch | armv7l |
| timezone | America/Los_Angeles |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.32.1 |
| Stage | running |
| Available Repositories | 1276 |
| Downloaded Repositories | 6 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | February 2, 2024 at 4:00 PM |
| relayer_connected | true |
| relayer_region | us-east-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | true |
| google_enabled | false |
| remote_server | us-east-1-8.ui.nabu.casa |
| certificate_status | ready |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 10.3 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.06.2 |
| agent_version | 1.5.1 |
| docker_version | 23.0.6 |
| disk_total | 28.6 GB |
| disk_used | 9.0 GB |
| healthy | true |
| supported | true |
| board | rpi2 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Mosquitto broker (6.2.1), Z-Wave JS UI (1.13.4), File editor (5.6.0), Samba share (10.0.2), ESPHome (2023.6.0), Advanced SSH & Web Terminal (15.0.2) |
Dashboards
| dashboards | 4 |
|---|---|
| resources | 4 |
| views | 14 |
| mode | storage |
Recorder
| oldest_recorder_run | June 15, 2023 at 3:56 PM |
|---|---|
| current_recorder_run | June 22, 2023 at 10:13 AM |
| estimated_db_size | 442.69 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
Supervisor diagnostics
config_entry-hassio-d50e495cb6f0125fed2e5c63db2106b6.json.txt
Additional information
Home Assistant Core logs:
Logger: homeassistant.components.websocket_api.http.connection
Source: components/hassio/update.py:169
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:34:54 PM (2 occurrences)
Last logged: 2:35:44 PM
[1704455400] Error updating ESPHome: Can't install ghcr.io/esphome/esphome-hassio:2023.4.3: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.4.3/json: Not Found ("No such image: ghcr.io/esphome/esphome-hassio:2023.4.3")
[1521728168] Error updating ESPHome: Can't install ghcr.io/esphome/esphome-hassio:2023.4.3: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.4.3/json: Not Found ("No such image: ghcr.io/esphome/esphome-hassio:2023.4.3")
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 167, in async_install
await async_update_addon(self.hass, slug=self._addon_slug, backup=backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/handler.py", line 52, in _wrapper
raise HassioAPIError(data["message"])
homeassistant.components.hassio.handler.HassioAPIError: Can't install ghcr.io/esphome/esphome-hassio:2023.4.3: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.4.3/json: Not Found ("No such image: ghcr.io/esphome/esphome-hassio:2023.4.3")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1849, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1889, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 226, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 798, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 981, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 838, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 156, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 417, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/hassio/update.py", line 169, in async_install
raise HomeAssistantError(f"Error updating {self.title}: {err}") from err
homeassistant.exceptions.HomeAssistantError: Error updating ESPHome: Can't install ghcr.io/esphome/esphome-hassio:2023.4.3: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.4.3/json: Not Found ("No such image: ghcr.io/esphome/esphome-hassio:2023.4.3")
Host Logs:
May 03 21:34:53 homeassistant dockerd[473]: time="2023-05-03T21:34:53.828932024Z" level=info msg="Attempting next endpoint for pull after error: no matching manifest for linux/arm/v6 in the manifest list entries"
Previously I had an issue opened in core.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 4
- Comments: 40 (8 by maintainers)
Commits related to this issue
- Set Raspberry Pi 2 Supervisor architecture correctly The Raspberry Pi 2 was based on Cortex-A7 in first revisions, then Cortex-A53. However, both ar armv7 architectures, and that is also how the Oper... — committed to home-assistant/operating-system by agners 6 months ago
- Set Raspberry Pi 2 Supervisor architecture correctly (#3012) The Raspberry Pi 2 was based on Cortex-A7 in first revisions, then Cortex-A53. However, both ar armv7 architectures, and that is also how... — committed to home-assistant/operating-system by agners 6 months ago
- Set Raspberry Pi 2 Supervisor architecture correctly (#3012) The Raspberry Pi 2 was based on Cortex-A7 in first revisions, then Cortex-A53. However, both ar armv7 architectures, and that is also how... — committed to home-assistant/operating-system by agners 6 months ago
Ok, this is definitely not Docker default issue.
It seems the Supervisor is falling back to the Supervisor architecture itself: https://github.com/home-assistant/supervisor/blob/2023.12.0/supervisor/docker/interface.py#L231
However, for Raspberry Pi 2 this should be armv7. But it seems that the OS is using the Supervisor image is declared as
armhf(see https://github.com/home-assistant/operating-system/blob/11.2/buildroot-external/board/raspberrypi/rpi2/meta#L11), which is translated tolinux/arm/v6in Docker multi-arch.So there are two issue here:
armv7variant of the Supervisor.As for 2.) since we declare compatibility for
armv7andarmhffor Raspberry Pi 2 in Supervisor this change will still allow to install the same images. The only difference will be that locally built images will default to armv7 from then on-wards.This has not been fixed still. Having the same issue upgrading from 2023.8.2 to 2023.9.3.
So I’m replying with 👎 so you don’t close this unresolved issue.
Still broken on raspberry pi 2 though which this thread as about.
@agners Today I received ESPhome 2023.12.0 update and out of the sudden this worked fine. Seems, the problem is gone without removing the add-on. So, whoever contributerd to 12.0, thanks a lot
There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still not resolved. Same error when updating to version esphome-hassio:2023.10.3 (homeassistant: core-2023.10.5, supervisor-2023.10.0). All other updates work fine. Problem is already 8 months old, was first mentioned one 1 march 2022 here and then here.
There hasn’t been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
I’m actually doing
docker pull ghcr.io/esphome/esphome-hassio:2023.5.5via SSH (replace “2023.5.5” with the latest esphome version number visible in the home assistant UI)But yep, the issue is still there and it is quite annoying. Someone please fix it. I believe the fix is rather easy. Someone just broke
armv7larch.Still unsolved when upgrading to 2023.8.1:
Can’t install ghcr.io/esphome/esphome-hassio:2023.8.1: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.8.1/json: Not Found (“No such image: ghcr.io/esphome/esphome-hassio:2023.8.1”)
Raspbeery Pi 2, all other upgrades working fine. Work around: delete add-on Esphome en install it again (no setting are lost).
Oh I actually forgot, there was also a fix in HAOS which fixes the same problem (https://github.com/home-assistant/operating-system/pull/3012). So essentially, if either of this is true, the ESPHome update should work again on Raspberry Pi 2:
@007hacky007 the fix is in Supervisor 2023.12.1 which is at this point in the beta channel.
@peterhanssens I am assuming you have the beta channel enabled then?
The problem of “buteomont” was different. He couldn’t do any updates, apparently it was a DNS problem for him. Our problem is different. All other updates work. A non-existent update package is called when updating esphome. I think our error only occurs with ARMv7l (like with raspberry pi2).
Still unsolved, same error when upgrading to 2023.8.2 en now also 2023.8.3. Work around: delete add-on Esphome en install it again (no setting are lost). All other upgrades work fine. Not a big problem, but just to keep this bug alive.
Again upgrade not working: Can’t install ghcr.io/esphome/esphome-hassio:2023.6.4: 404 Client Error for http+docker://localhost/v1.42/images/ghcr.io/esphome/esphome-hassio:2023.6.4/json: Not Found (“No such image: ghcr.io/esphome/esphome-hassio:2023.6.4”)
But uninstall en install again works to upgrade (Raspberry Pi 2), all other upgrades working fine.