2022.7.x docker container broken on 1st gen Raspberry Pi

The problem

I’m trying to run home-assistant:stable with the docker compose method on an Raspberry Pi Model B Rev 2 (512MB RAM / armv6l). This is obviously not a good platform, but it’s what I had available for a test. The OS is Raspbian/bullseye, with docker ce 20.10.17

Running docker compose up, the container starts, but the homeassistant inside seems to crash:

Attaching to homeassistant
homeassistant  | s6-rc: info: service s6rc-oneshot-runner: starting
homeassistant  | s6-rc: info: service s6rc-oneshot-runner successfully started
homeassistant  | s6-rc: info: service fix-attrs: starting
homeassistant  | s6-rc: info: service fix-attrs successfully started
homeassistant  | s6-rc: info: service legacy-cont-init: starting
homeassistant  | s6-rc: info: service legacy-cont-init successfully started
homeassistant  | s6-rc: info: service legacy-services: starting
homeassistant  | services-up: info: copying legacy longrun home-assistant (no readiness notification)
homeassistant  | s6-rc: info: service legacy-services successfully started
homeassistant  | [22:08:03] INFO: Home Assistant Core finish process exit code 256
homeassistant  | [22:08:03] INFO: Home Assistant Core finish process received signal 4
homeassistant  | [22:08:09] INFO: Home Assistant Core finish process exit code 256
homeassistant  | [22:08:09] INFO: Home Assistant Core finish process received signal 4

A plain Home Assistant Core venv starts successfully on the same hardware, as does the previous release of the docker container using 2022.6.6@sha256:c2e7c0bb84e6f84d1c62ff34d9f286fb17486ccf2760a5612f65128848c59316.

What version of Home Assistant Core has the issue?

2022.7.5

What was the last working version of Home Assistant Core?

2022.6.6

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

When looking at the resulting core file with gdb, it reports an illegal instruction:

Core was generated by `python3 -m homeassistant --config /config'.
Program terminated with signal SIGILL, Illegal instruction.
#0  0xb58fe7fa in ?? ()

I assume the build uses some compiler flag that creates instructions not supported by the BCM2835?

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Wetzel402]

I confirmed this problem still exists on 2022.11.5. I tried to build 2022.11.5 on my QNAP NAS but so far I haven’t been able to. I’m a noob when it comes to building from source. I tried downloading the HA core repo and adding the build command to my docker compose but it gives me an error saying I need to check my yaml. I will build on my machine if I can figure it out.

[AloneLiberty]

I’ve done some investigation about this issue, the issue is deeper than cryptography and numpy. It is expanded on all packages with compiled (С/C++/Rust) code. When I recompiled packages on my Pi 0W, it seems to work. But what is strange - I tried to build through Github Actions and packages also work from it. I don’t know why packages from Home Assistant wheels index doesn’t work, maybe it was temporary compiler issue (like https://github.com/piwheels/packages/issues/276). Can someone else try to compile numpy or any other failing packages on Github Actions and confirm/refute my theory? If the theory is true, we should ask developers to rebuild all armhf packages and issue will be solved.