Modern distros might prevent to use pip install XXX as root (as we do in EnOSlib)
For example debian12 supports the pep0668 and thus prevent to use pip intall XXX
as root.
So currently some part of EnOSlib are broken because we use pip install
as root behind the scene (e.g the docker service make sure that the docker python client is installed on the node using pip as root)
Also As a Enoslib's user using pip install
or Ansible pip module will likely breaks (by default run as root)
Possible solutions include:
- removing the
EXTERNALLY-MANAGED
managed file as this will fallback to the previous behaviour (located in /usr/lib/python3.XX/EXTERNALLY-MANAGED) - making sure we install dependencies in a clean way (venv, user home ...)