I'm trying to find out why updating from 11.X to 12.X broke my custom integration. It require the following package : gtfs-realtime-bindings==1.0.0 but when trying to debug why the installation failed, I realized that HA use the following command : python3 -m pip install --quiet gtfs-realtime-bindings==1.0.0 --index-strategy unsafe-first-match --upgrade --constraint /usr/src/homeassistant/homeassistant/package_constraints.txt --target /config/deps so by using --quiet it's almost impossible to know why it fail. Running the command manually does work weirdly enough. I tried the following debug options : homeassistant.loader: debug homeassistant.setup: debug homeassistant.util.package: debug
#Custom integrations, how to debug dependencies installation
26 messages · Page 1 of 1 (latest)
How are you running HA? HAOS? Docker? Podman? K8s? Something else?
Podman.
Yeah, that's a known feature/bug/whatever
Podman isn't detected as a container, so you have to work around it
Let me see if I can find the link
The whole issue is a relevant read, as is https://community.home-assistant.io/t/wth-is-going-on-with-docker-container-installs-and-third-party-integrations-that-need-python-modules/806430
It's an "interesting" one where the official line is that any compliant container tech can be used, but HA only supports Docker...
Wow thank you
It’s interesting indeed docker vs OCI compliant.
Container used to be the best way to install HA. Damn time has passed.
Container still is IMO, but for some reason recent changes broke detection for non-Docker containers
I think I read somewhere it is the passage to uv? Since 1024.10.X?
Yeah
The issue originates from the introduction of uv as the package manager we now use for Python.
GitHub
Proposed change
Improve is docker env checks
Check for the existence of the /run/.containerenv file. This file is created by podman (https://github.com/containers/podman/blob/v5.3.1/docs/source/ma...
So basically all new installations of custom components will break. At least old ones the packages are already installed.
Well, yes, but just apply the trivial workaround 😉
That explains the higher headache count I have since 2 months. 😅
At least I try to avoid as much as possible custom stuff.
Will try that indeed.
I mean, it's a simple volume mount... not very "custom", but I get where you're coming from
Oh no I mean custom integrations requiring modules installation at runtime.
Ah... I have quite a few, but I stopped worrying about that a long time ago
I joined the discord for this exact issue. I recently moved to podman + quadlet and custom integrations were reportting missing deps. I saw the packages in the deps folder and ended up manually installing the packages in the container. I hope this gets fixed.