Matter Server 9.1.0 and 9.1.1: node binary in aarch64 image is 88 MiB (SIGBUS on startup) — add-on fails to start

[mdetheridge]

Describe the issue you are experiencing

The Matter Server add-on (9.1.1) fails to start on aarch64. The bundled Node
runtime crashes with SIGSEGV/SIGBUS before executing any JavaScript, so the
add-on enters a watchdog restart loop.

The node binary in homeassistant/aarch64-addon-matter-server:9.1.1 is
92,274,688 bytes — exactly 88 MiB — while the official Node 24.18.0 arm64
binary that the base image installs is 121,723,800 bytes. The sha256 sums
differ. Mapping an ELF whose file is shorter than its program headers
declare produces SIGBUS, which matches the observed failure.

This reproduces after docker image prune -a and a fresh pull, so it is not
local layer corruption.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Matter Server

What is the version of the app?

9.1.1

Steps to reproduce the issue

$ docker run --rm --entrypoint node \
    homeassistant/aarch64-addon-matter-server:9.1.1 -e "console.log('ok')"; echo "exit=$?"
exit=139

$ docker run --rm --entrypoint ls \
    homeassistant/aarch64-addon-matter-server:9.1.1 -la /usr/local/bin/node
-rwxr-xr-x 1 root root 92274688 Jun 23 19:44 /usr/local/bin/node

$ docker run --rm --entrypoint ls arm64v8/node:24.18.0-slim -la /usr/local/bin/node
-rwxr-xr-x 1 root root 121723800 Jun 23 19:44 /usr/local/bin/node

$ docker run --rm --entrypoint sha256sum \
    homeassistant/aarch64-addon-matter-server:9.1.1 /usr/local/bin/node
7ac6c8e6abaf09e1178362546c4a2ee8b883db492fc5436d06c3259dff535fdf

$ docker run --rm --entrypoint sha256sum arm64v8/node:24.18.0-slim /usr/local/bin/node
6bf69d0eda41a12030d5f28d958cd09ce323bc0c13f1ab4d8bb426933aa08812

Official arm64v8/node:24.18.0-slim runs correctly on the same host and kernel:

$ docker run --rm arm64v8/node:24.18.0-slim node -e "console.log(process.version,'ok')"
v24.18.0 ok

ldd /usr/local/bin/node inside the add-on image exits 135 (SIGBUS).
LD_DEBUG=libs produces no output at all, indicating the crash occurs during
segment mapping, before dynamic linking begins. The file reads end-to-end
without I/O error, and all shared libraries it would need are present in the
image (libatomic.so.1, libstdc++.so.6, libgcc_s.so.1, libm.so.6, libcrypto.so.3).

Image manifest digest: sha256:73ad4d1aa86a0de2e4582329f35aa74a8a87a3e0baa0cee13957766d1b847922
Image architecture reports arm64 linux, so this is not an arch mismatch.

System Health information

There are currently no repairs pending

Anything in the Supervisor logs that might be useful for us?

2026-08-02 20:46:26.672 INFO (MainThread) [supervisor.docker.app] Starting Docker app homeassistant/aarch64-addon-matter-server with version 9.1.1
2026-08-02 20:46:26.773 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_matter_server
2026-08-02 20:46:26.785 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2026-08-02 20:46:29.882 ERROR (MainThread) [supervisor.apps.app] App Matter Server exited with non-zero exit code 139
2026-08-02 20:46:29.884 WARNING (MainThread) [supervisor.apps.app] Watchdog found app Matter Server exited with code 139, restarting...
2026-08-02 20:46:29.886 INFO (MainThread) [supervisor.docker.manager] Cleaning app_core_matter_server application
2026-08-02 20:46:29.955 INFO (MainThread) [supervisor.docker.app] Starting Docker app homeassistant/aarch64-addon-matter-server with version 9.1.1
2026-08-02 20:46:30.062 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_matter_server
2026-08-02 20:46:30.074 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2026-08-02 20:46:33.172 ERROR (MainThread) [supervisor.apps.app] App Matter Server exited with non-zero exit code 139
2026-08-02 20:46:33.174 WARNING (MainThread) [supervisor.apps.app] Watchdog found app Matter Server exited with code 139, restarting...
2026-08-02 20:46:33.175 INFO (MainThread) [supervisor.docker.manager] Cleaning app_core_matter_server application
2026-08-02 20:46:33.257 INFO (MainThread) [supervisor.docker.app] Starting Docker app homeassistant/aarch64-addon-matter-server with version 9.1.1
2026-08-02 20:46:33.372 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_matter_server
2026-08-02 20:46:33.387 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2026-08-02 20:46:36.474 ERROR (MainThread) [supervisor.apps.app] App Matter Server exited with non-zero exit code 139
2026-08-02 20:46:36.475 WARNING (MainThread) [supervisor.apps.app] Watchdog found app Matter Server exited with code 139, restarting...
2026-08-02 20:46:36.477 INFO (MainThread) [supervisor.docker.manager] Cleaning app_core_matter_server application
2026-08-02 20:46:36.552 INFO (MainThread) [supervisor.docker.app] Starting Docker app homeassistant/aarch64-addon-matter-server with version 9.1.1
2026-08-02 20:46:36.656 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_matter_server
2026-08-02 20:46:36.668 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server
2026-08-02 20:46:39.759 ERROR (MainThread) [supervisor.apps.app] App Matter Server exited with non-zero exit code 139
2026-08-02 20:46:39.761 WARNING (MainThread) [supervisor.apps.app] Watchdog found app Matter Server exited with code 139, restarting...
2026-08-02 20:46:39.762 INFO (MainThread) [supervisor.docker.manager] Cleaning app_core_matter_server application
2026-08-02 20:46:39.832 INFO (MainThread) [supervisor.docker.app] Starting Docker app homeassistant/aarch64-addon-matter-server with version 9.1.1
2026-08-02 20:46:39.940 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from core_matter_server
2026-08-02 20:46:39.951 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from core_matter_server

Anything in the app logs that might be useful for us?

s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service matter-server: stopping
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
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 banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
-----------------------------------------------------------
 Add-on: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 9.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 18.2  (aarch64 / qemuarm-64)
 Home Assistant Core: 2026.7.4
 Home Assistant Supervisor: 2026.07.5
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
[20:46:30] INFO: Starting Matter Server...
[20:46:30] INFO: Time sync 'auto': host NTP is synchronized, enabling time sync.
s6-rc: info: service legacy-services successfully started
[20:46:30] INFO: Using 'enp0s2' as primary network interface.
[02:46:30] WARNING: matter-server service exited with code 139 (by signal 11).

Additional information

No response

[mdetheridge]

Additional data point: 9.0.4 works correctly on the same host.

$ docker run --rm --entrypoint node \
    homeassistant/aarch64-addon-matter-server:9.0.4 -e "console.log('ok')"; echo "exit=$?"
ok
exit=0

$ docker run --rm --entrypoint node \
    homeassistant/aarch64-addon-matter-server:9.1.0 -e "console.log('ok')"; echo "exit=$?"
exit=139

9.1.0 does not. So, something broke in 9.1.0

[Apollon77]

9.1.0 is used by several 100k users, same for the other versions. I assume a corrupted docker download or such. Does 9.1.1. work?

[agners]

This reproduces after docker image prune -a and a fresh pull, so it is not
local layer corruption.

This is not proof that there is no local corruption.

Note that deleting and re-pulling the affected image does not necessarily help: image layers are shared between images and reused across versions, and docker pull skips layers it believes are already present locally.

To recover, make a full backup, download it, then reinstall HomeAssistant OS and restore the backup. A dedicated feature to reset the Docker image storage is tracked in#6555.