Removing the config/lsiopy dir worked.
I do see permission warnings about config/.cache/pip though, which is not a big deal, but still floods the logs.
homeassistant | WARNING: The directory '/config/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Is this secondary venv supposed to be automatically generated on runtime? I ask because naturally my /config is preserved after the container is stopped, so i’m wondering how upgrades will deal with this from one python release to the next.
Secondary venv is created on container start (the first time) because it resides in /config, persistent storage.
Cache issue is harmless, pip doesn’t really need a cache folder (we always run it with --no-cache-dir but I guess HA doesn’t). Any case, it doesn’t cause any harm. You can try creating that folder in your config folder and it might get rid of the log messages. As long as it exists, its perms should be fixed on container start.
Python upgrades should be fine because all the python packages in that venv reside in a folder that has the python version in its name so packages are kept separated by python version.