home-assistant/core

24.10.3 arm64 docker image fails to start

Opened this issue · 1 comments

Foggy2 commented

The problem

I am using docker on my Raspberry Pi 4B and running the Home Assistant Core image. Each night a cron job runs that updates the current images and rebuilds the containers. This has been in place and working for several months without issue.

Today I have discovered that the Home Assistant Core container no longer starts successfully. When I check the container logs using command docker container logs homeAssistant the only entry shown is exec /init: exec format error.

The docker compose configuration that I am using is:

homeassistant:
    image: ghcr.io/home-assistant/home-assistant:stable
    container_name: homeAssistant
    restart: unless-stopped
    privileged: true
    volumes:
      - ./homeassistant/config:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    devices:
    - /dev/ttyUSB0:/dev/ttyUSB0
    network_mode: host
    environment:
      TZ: Australia/Adelaide

I checked the logs from my cron job and saw that last night a new image was pulled for Home Assistant so I believe I am currently attempting to run image 2024.10.3. Docker reports that the current stable image that is failing to start has image ID sha256:fe0b5738d0de2b29a51e9cacede3c4ae2c870492cdd061e27240be0695e622ac.

As such, I have amended the image in my Docker Compose file to point at image: ghcr.io/home-assistant/home-assistant:2024.10.2 and the container now successfully starts again.

What version of Home Assistant Core has the issue?

core-2024.10.3

What was the last working version of Home Assistant Core?

core-2024.10.2

What type of installation are you running?

Home Assistant Container

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

crsang commented

I experienced this same issue. Rolled back to 10.2.