[BUG] not starting after upgrade

[loki666]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

since last upgrade, my homeassitant container is not starting

Expected Behavior

should starts

Steps To Reproduce

upgrade to latest

Environment

- OS: Linux
- How docker service was installed:

CPU architecture

x86-64

Docker creation

docker create --log-opt max-size=10m --name=homeassistant --net=host -e PUID=99 -e PGID=99 -e TZ=Europe/Brussels -v /var/docker/appdata/homeassistant:/config lscr.io/linuxserver/homeassistant:latest

Container logs

Creating venv in /config/lsiopy for runtime use
Updating pip to HA supported version
Collecting pip<22.1,>=21.0
  Downloading pip-22.0.4-py3-none-any.whl (2.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 10.2 MB/s eta 0:00:00
Requirement already satisfied: setuptools in /config/lsiopy/lib/python3.11/site-packages (65.5.0)
Collecting setuptools
  Downloading setuptools-68.0.0-py3-none-any.whl (804 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 804.0/804.0 kB 10.6 MB/s eta 0:00:00
Collecting wheel
  Downloading wheel-0.40.0-py3-none-any.whl (64 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.5/64.5 kB 10.6 MB/s eta 0:00:00
Installing collected packages: wheel, setuptools, pip
  Attempting uninstall: setuptools
    Found existing installation: setuptools 65.5.0
    Uninstalling setuptools-65.5.0:
      Successfully uninstalled setuptools-65.5.0
  Attempting uninstall: pip
    Found existing installation: pip 23.1.2
    Uninstalling pip-23.1.2:
      Successfully uninstalled pip-23.1.2
Successfully installed pip-22.0.4 setuptools-68.0.0 wheel-0.40.0
Setting permissions
[custom-init] No custom files found, skipping...
Traceback (most recent call last):
  File "/lsiopy/bin/hass", line 5, in <module>
    from homeassistant.__main__ import main
ModuleNotFoundError: No module named 'homeassistant'

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[loki666]

duplicate of #82 (sorry)