Supervisor fails to start HA Core

[wipmate]

Similar to others in the past (1, 2, 3), I have recently encountered an issue where suddenly the HA Supervisor would fail to start HA Core. The logs would show the following repeated failure:

s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error

While I have successfully recovered the system from this state twice by stopping and removing the hassio_supervisor docker container, leading to its recreation, this seemed more like a workaround. Rebooting the system does not fix the issue.

Would it be reasonable to implement a repair mechanism for this specific error state?

Supervisor logs

$ docker container ls
aa6b5a3c30f3   ghcr.io/home-assistant/aarch64-hassio-supervisor:latest    "/init"               About an hour ago   Up 5 minutes                                             hassio_supervisor
89b4195da489   ghcr.io/home-assistant/aarch64-hassio-observer:2025.02.0   "/usr/bin/observer"   7 months ago        Up 5 minutes   0.0.0.0:4357->80/tcp, [::]:4357->80/tcp   hassio_observer

$ docker logs aa6b5a3c30f3
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
s6-supervise supervisor: warning: unable to spawn ./run (waiting 60 seconds): Exec format error
...

System information

version	core-2025.11.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	aarch64
user	root
virtualenv	false
python_version	3.13.9
os_name	Linux
os_version	6.6.74-haos-raspi
arch	aarch64
timezone	Europe/Berlin
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2426
Downloaded Repositories	15

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 15.0
update_channel	stable
supervisor_version	supervisor-2025.11.4
agent_version	1.7.2
docker_version	28.0.1
disk_total	28.5 GB
disk_used	15.5 GB
nameservers	192.168.178.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	Studio Code Server (6.0.0), ESPHome Device Builder (2025.11.0), Mosquitto broker (6.5.2), Let's Encrypt (5.4.9), Terminal & SSH (9.20.1)

Dashboards

dashboards	2
resources	8
views	5
mode	storage

Recorder

oldest_recorder_run	November 5, 2025 at 10:01
current_recorder_run	November 22, 2025 at 03:05
estimated_db_size	359.50 MiB
database_engine	sqlite
database_version	3.49.2

[mseelye]

I'm attempting to confirm I have a similar setup and issue here. I'm running HA on an rpi5 with a recent HA update (currently shows core-2025.11.2 and supervisor-2025.11.4).

I suddenly started experiencing this and seeing this in the observer:

s6-supervise watchdog: warning: unable to spawn ./run (waiting 60 seconds): Exec format error

Attempts to start/stop all the containers (from the emergency CLI) result in a severely crippled environment.

I have not tried wipmate's workaround of stopping and removing the supervisor container yet though.

Any additional advice on a remedy is appreciated.
Thanks!

Update:
I stopped the supervisor container, and rebooted the system and it came up normally. I will continue to monitor this thread for updates as I suspect it'll happen again.

[alsternerd]

Had the same issue just now and stopping the supervisor container, then rebooting did solve it.
That's odd.