I had running for a long time HA on an RPi using docker compose on Debian (bookworm). It was working fine, I could also update it. Now I tried to update to the latest release and I get this when starting home assistant:
13:32:34] INFO: Installing uv into venv
uv 0.9.6
Using Python 3.13.9 environment at: /usr/local
Using Python 3.13.9 environment at: /var/tmp/homeassistant-venv
× No solution found when resolving dependencies:
╰─▶ Because uv==0.9.6 has no wheels with a matching platform tag (e.g., `linux_aarch64`) and you require uv==0.9.6, we can conclude that your requirements are
unsatisfiable.
hint: `uv` was found on https://wheels.home-assistant.io/musllinux-index/, but not at the requested version (uv==0.9.6). A compatible version may be available
on a subsequent index (e.g., https://pypi.org/simple). By default, uv will only consider versions that are published on the first index that contains a given
package, to avoid dependency confusion attacks. If all indexes are equally trusted, use `--index-strategy unsafe-best-match` to consider all versions from all
indexes, regardless of the order in which they were defined.
hint: Wheels are available for `uv` (v0.9.6) on the following platform: `musllinux_1_1_x86_64`
[13:32:34] INFO: Home Assistant Core finish process exit code 123
[13:32:34] INFO: Home Assistant Core service shutdown
Downgrading the image to 2025.10 doesn’t work either, I run into a similar error:
× No solution found when resolving dependencies:
╰─▶ Because there is no version of uv==0.8.9 and you require uv==0.8.9, we can conclude that your requirements are unsatisfiable.
Indeed Home Assistant Wheels has 0.9.6 for x86_64 only.
Is there a quick way to get back a working homeassistant (unfortunately I pruned the old, working images)?
I haven’t dug further, but I’d guess either the HASS team accidentally only provided an x86_64 wheel of uv in the latest update of its index (most other packages there have architecture-agnostic wheels) or that default index resolution strategy of uv has changed recently, either of which has resulted in homeassistant-docker-venv recently breaking. I’ll research more, but right now I’m not sure which upstream needs to resolve the issue. (homeassistant-docker-venv, which isn’t officially part of the HASS project, might just need to update their script as below, depending on whether HASS intends to ever provide uv wheels for all architectures again.)
Regardless, for now, patching the run script from homeassistant-docker-venv works just fine. Replace this:
This allows uv to search each index in its list rather than just home-assistant.io/musllinux-index, approximating the default behavior of pip (--index https://pypi.org/simple also works.)
