Open binkleyz2 opened 8 months ago
Hmm, did you upgrade this system from Bullseye to Bookworm? I am wondering how pip
and the docker-compose
module were installed in the first place without the related override for this pip
block in place.
However, do the following and then retry:
grep -q '\[global\]' /etc/pip.conf 2> /dev/null || printf '%b' '[global]\n' | sudo tee -a /etc/pip.conf > /dev/null
sudo sed -i '/^\[global\]/a\break-system-packages=true' /etc/pip.conf
Actually, yes, I did just recently upgrade to bookworm using the script here: https://dietpi.com/blog/?p=3128
I ran the two commands provided and it seems to be fine now.
Created a post-install debug report in case you want to see it - d974e242-9339-477c-9c94-fb614a3fa65d
Did you install Docker Compose via dietpi-software
before or manually? Python 3 should have been reinstalled, adding this setting to /etc/pip.conf
, but not if Python was installed manually. And now Docker Compose does not require Python anymore.
EDIT: Ah thanks for the debug upload. I'll have a look. We should be able to prevent this error when knowing the circumstances which lead to it.
I don't recall installing Docker Compose via the dietpi-software route before, and I also do not recall installing it manually, though that is a possibility..I've had this box up and running for a few years now and early on I was kind of just hacking at it to get functionality. I use the box primarily for a VPN server and PiHole/Unbound setup, but have recently wanted to expand what the box is doing so figured Docker would be a good path forward.
Creating a bug report/issue
Details:
Linux 617NUC 6.1.0-16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.67-1 (2023-12-12) x86_64 GNU/Linux
pip3 uninstall -y docker-compose
Steps to reproduce:
Expected behaviour:
Actual behaviour:
Extra details:
Additional logs:
× This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install.
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification.