HASS Docker Image unable to load on Raspberry Pi 5 (jemalloc)

[sieren]

The problem

When trying to boot up HASS in a Docker Environment on Raspberry Pi 5 this ultimately results in:

homeassistant  | <jemalloc>: Unsupported system page size
homeassistant  | <jemalloc>: Unsupported system page size
homeassistant  | <jemalloc>: Unsupported system page size
homeassistant  | Fatal Python error: _PyRuntimeState_Init: memory allocation failed
homeassistant  | Python runtime state: unknown
homeassistant  |
homeassistant  | [15:16:11] INFO: Home Assistant Core finish process exit code 1
homeassistant  | [15:16:11] INFO: Home Assistant Core service shutdown

I tried to figure whether jemalloc was disabled specifically for RPI 4 (which is where this container ran on before) but could not find any relevant parts of the code.

For now adding

    environment:
      - DISABLE_JEMALLOC=true

to docker-compose.yml seems to be an acceptable workaround.

What version of Home Assistant Core has the issue?

core-2023.10.5

What was the last working version of Home Assistant Core?

core-2023.10.5

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

[mib1185]

the pi 5 is not supported, yet.
See: https://www.home-assistant.io/blog/2023/10/17/expected-support-for-raspberry-pi-5
in this blog post, you will also find a linkt to the GitHub discussion about hardware support of pi 5 😉

[sieren]

Thanks. I saw the discussion but I figured it was more about HASS OS rather than the docker image :)
Anyway, thanks for clarifying. Figured the workaround might help folks who run HASS already via Docker.

[mib1185]

I found this in the docs about possible issues with jemalloc when using the docker image:
https://www.home-assistant.io/installation/raspberrypi#optimizations

[niggowai]

I'm experiencing the same issues on Asahi Linux, since Apple Silicon also has 16k pages. i worked around it by recompiling and reinstalling jemalloc in the container using a Dockerfile
Hope that helps for HA to support more page sizes soon.
Since jemalloc doesn't allow Dynamic page sizes now and in the future, jemalloc/jemalloc#467, there must be provided more docker images with different page sizes.

@sieren FYI You may head over to the Asahi Linux Software Support Site which lists the Software broken and fixed for 16k pages

[PatrickTetz]

Hey, I am not sure how much merit there is to this statement, but if it is true, the fix should be trivial:

Jemalloc supports using a smaller runtime page size than it was compiled with. So we simply always increase the page-size on arm64.

Source

@sieren, the environment flag you mentioned to solve the issue temporarily is only for the HASS image, I assume? I am stuck with the supervisor image, and the flag is not working. Unfortunately, they also have the same jemalloc issue.

[sieren]

@PatrickTetz Indeed, I haven't verified this on the supervisor image, just the regular ol' HASS docker image

[ohadlevy]

@sieren, the environment flag you mentioned to solve the issue temporarily is only for the HASS image, I assume? I am stuck with the supervisor image, and the flag is not working. Unfortunately, they also have the same jemalloc issue.

@PatrickTetz raspberrypi/bookworm-feedback#107 (comment) worked for me

[PatrickTetz]

@ohadlevy this seems to work great, thanks for sharing!