error: externally-managed-environment: This environment is externally managed #2201

robfantini · 2023-07-11T22:16:04Z

Describe the bug
All I have is the output from trying to start bazarr :

#  /opt/bazarr/bin/python3 /opt/bazarr/bazarr.py
Bazarr starting...
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
2023-07-11 18:09:16,830 - root                             (7f905a2a02c0) :  INFO (init:88) - BAZARR installing requirements...
2023-07-11 18:09:17,087 - root                             (7f905a2a02c0) :  ERROR (init:97) - BAZARR requirements.txt installation result: b'error: externally-managed-environment\n\n\xc3\x97 This environment is externally managed\n\xe2\x95\xb0\xe2\x94\x80> To install Python packages system-wide, try apt install\n    python3-xyz, where xyz is the package you are trying to\n    install.\n    \n    If you wish to install a non-Debian-packaged Python package,\n    create a virtual environment using python3 -m venv path/to/venv.\n    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make\n    sure you have python3-full installed.\n    \n    If you wish to install a non-Debian packaged Python application,\n    it may be easiest to use pipx install xyz, which will manage a\n    virtual environment for you. Make sure you have pipx installed.\n    \n    See /usr/share/doc/python3.11/README.venv for more information.\n\nnote: 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.\nhint: See PEP 668 for the detailed specification.\n'
Bazarr exited.

To Reproduce
Steps to reproduce the behavior:

let bazarr uprade from 1.2.2 to 1.2.3
start it up: /opt/bazarr/bin/python3 /opt/bazarr/bazarr.py

Software (please complete the following information):

Bazarr: 1.2.3
OS: Debian 12

Notes:
I checked the requirements.txt file for 1.2.2 and 1.2.3 and they are the same.

I have a test system set up and running in order to do any tests you may want .

Let me know if there is more info wanted or testing to try to fix.

thank you for this software.

Additional context
Add any other context about the problem here.

The text was updated successfully, but these errors were encountered:

morpheus65535 · 2023-07-12T02:04:21Z

Seems to be related to upgrade of your system: https://stackoverflow.com/questions/75602063/pip-install-r-requirements-txt-is-failing-this-environment-is-externally-manag

robfantini · 2023-07-12T08:58:43Z

I did have bazarr working before 1.2.3 . the system started as Debian 12 when I initially installed bazarr . at that point I had to do these


apt install python3-full mediainfo  
python3 -m venv /opt/bazarr/

```
`

also this is the systemd service.  note full path names

`
/etc/systemd/system/bazarr.service :
[Unit]
Description=Bazarr Daemon
#After=syslog.target network.target

After=network.target sonarr.service radarr.service

[Service]
WorkingDirectory=/opt/bazarr/
User=htuser
Group=user
UMask=0002
Restart=on-failure
RestartSec=5
Type=simple
ExecStart=/opt/bazarr/bin/python3 /opt/bazarr/bazarr.py
KillSignal=SIGINT
TimeoutStopSec=20
SyslogIdentifier=bazarr
ExecStartPre=/bin/sleep 30

[Install]
WantedBy=multi-user.target

`

morpheus65535 · 2023-07-12T11:57:58Z

Bazarr 1.2.3 have a new requirement. It's been a long time since we added one so it's normal. Now, you operating system tell to Python to refuse to install requirements without using a venv. The other solution is to delete the file that instruct Python to refuse installation of requirements as instructed in the link I provided.

robfantini · 2023-07-12T12:07:18Z

Okay I'll check the link and try to undo the venv stuff later on.

Also /opt/bazarr//requirements.txt on both systems is identical .
[ except on the new one I had edited it to remove an error and ended up with a line feed after Pillow>=9.0.0 . that should not make a difference ]
you mentioned there is a new requirement, should that be in the /opt/bazarr//requirements.txt file?

morpheus65535 · 2023-07-12T12:11:42Z

In v1.2.3, requirements.txt looks like that: https://github.com/morpheus65535/bazarr/blob/master/requirements.txt

robfantini · 2023-07-12T12:18:44Z

Okay I adjusted this line in requrements.txt , the rest were the same.
Pillow>=9.0.0 --only-binary=Pillow

still same error on startup using .

I can work on eliminating the venv setup in the evening or tomorrow. will need to research how to undo it...

morpheus65535 · 2023-07-12T14:10:32Z

You don't need to eliminate the venv, you must use it or disable PEP-668 by deleting the EXTERNALLY-MANAGED marker file: https://peps.python.org/pep-0668/#marker-file

morpheus65535 · 2023-07-31T11:40:55Z

Anything else to fix here?

robfantini · 2023-07-31T12:51:52Z

Hello,
I just read https://peps.python.org/pep-0668/#marker-file again.

regarding:
'disable PEP-668 by deleting the EXTERNALLY-MANAGED marker file' - I could not find that file in the paths suggested by the link.
Could you give me some clues where the file may be and its' name?

morpheus65535 · 2023-07-31T12:56:02Z

@robfantini first result in Google: https://stackoverflow.com/questions/75608323/how-do-i-solve-error-externally-managed-environment-everytime-i-use-pip3

morpheus65535 · 2023-08-04T19:00:04Z

No news, good news!

imthenachoman · 2023-10-13T03:14:21Z

This is what I had to do on Debian 12.

$ sudo apt install python3-dev python3-pip python3-distutils unrar unzip
$ wget https://github.com/morpheus65535/bazarr/releases/latest/download/bazarr.zip
$ sudo mkdir /opt/bazarr
$ sudo unzip bazarr.zip -d /opt/bazarr
$ cd /opt/bazarr
$ python3 -m venv .venv
$ source .venv/bin/activate
$ python3 -m pip install -r requirements.txt
$ sudo chown -R $USER:$USER /opt/bazarr
$ sudo nano /etc/systemd/system/bazarr.service

/etc/systemd/system/bazarr.service (notice the path to python3 in the ExecStart command):

[Unit]
Description=Bazarr Daemon
After=syslog.target network.target

# After=syslog.target network.target sonarr.service radarr.service

[Service]
WorkingDirectory=/opt/bazarr/
User=media
Group=media
UMask=0002
Restart=on-failure
RestartSec=5
Type=simple
ExecStart=/opt/bazarr/.venv/bin/python3 /opt/bazarr/bazarr.py
KillSignal=SIGINT
TimeoutStopSec=20
SyslogIdentifier=bazarr
ExecStartPre=/bin/sleep 30

[Install]
WantedBy=multi-user.target

$ sudo systemctl start bazarr
$ sudo systemctl status bazarr
$ sudo systemctl enable bazarr

I hope this helps others.

References:

ChristianMalazarte · 2023-10-25T11:52:51Z

For some reason, my .venv folder disappears when I restart the server and I have to recreate it again. Any clues as to why?

imthenachoman · 2023-10-25T12:17:45Z

Restart the bazarr app or your entire server? Where is your .venv folder? Super strange that it would be gone.

ChristianMalazarte · 2023-10-25T12:19:20Z

Restart the bazarr app or your entire server? Where is your .venv folder? Super strange that it would be gone.

Followed your instructions, so it's inside the /opt/bazarr/ folder. And restart computer not just the app.

imthenachoman · 2023-10-25T12:22:13Z

Try creating a file in /opt and /opt/bazarr and rebooting. Does it remove that file too? If so, then it must be something your OS is doing -- but I'm not sure why....

bmorgan99 · 2024-01-28T04:47:36Z

@imthenachoman
This is what I had to do on Debian 12...

I did this very thing for sabnzbd a few days ago and it worked fine. I have tried and re-tried it for bazarr but keep getting [Errno 13] Permission denied when trying to satisfy the requirements. I'm not keen on disabling python's new safeguards, so I'll try to hold out for a fix.

morpheus65535 · 2024-01-28T13:18:48Z

@bmorgan99 if you expect a fix on our side, you'll wait endlessly. There's nothing to fix on our side. The fix is disable the "safe guard" imposed by your operating system or use a venv.

imthenachoman · 2024-01-28T13:23:29Z

@morpheus65535 I'm not very familiar with all this but shouldn't Bazarr be updated to do what it needs to do to work with Python's safeguards?

morpheus65535 · 2024-01-28T13:30:35Z

@imthenachoman I agree, you're not very familiar with this. This isn't a Python safeguard, it an operating system requested feature that Python decided to honour. Python doesn't need that, the user is responsible to make sure the requirements have been installed or that Bazarr is able to do it by itself (by running the same pip command a user would have done). Bazarr can't alter your operating system configuration by itself, you must allow it do what it need.

imthenachoman · 2024-01-28T13:34:38Z

@morpheus65535 Ah. So this is a Debian thing. Got it. Thank you.

Then, I think it would be nice/kind if the Bazaar instructions included help/steps on what the end-user needs to do to get Bazarr to work on OSes that have this setting set. I understand if that's not possible as developers are busy but I think it would be kind/helpful.

morpheus65535 · 2024-01-28T13:36:16Z

@imthenachoman I agree, it would be nice and I'll happily accept a PR to the wiki page clarifying the required step.

imthenachoman · 2024-01-28T13:40:20Z

Cool. Hopefully someone is able to do that. I’m still not convinced what I did was the best approach. Thanks again!

bmorgan99 · 2024-02-02T08:39:10Z

For me, the fix was chown -R pi:pi /opt/bazarr for the install, then bazarr:bazarr after.
To run: /opt/bazarr/bazarr-venv/bin/python3 /opt/bazarr/bazarr.py

morpheus65535 added the awaiting feedback label Jul 31, 2023

morpheus65535 closed this as completed Aug 4, 2023

morpheus65535 changed the title ~~upgrade from 1.2.2 to 1.2.3 on Debian 12 caused bazarr to not be able to start~~ error: externally-managed-environment: This environment is externally managed Oct 13, 2023

morpheus65535 pinned this issue Oct 13, 2023

morpheus65535 mentioned this issue Dec 4, 2023

Bazarr se reinicia continuamente después de la instalación de requisitos en Raspberry Pi con Python 3.11 #2312

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error: externally-managed-environment: This environment is externally managed #2201

error: externally-managed-environment: This environment is externally managed #2201

robfantini commented Jul 11, 2023 •

edited

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023 •

edited

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023

morpheus65535 commented Jul 12, 2023

morpheus65535 commented Jul 31, 2023

robfantini commented Jul 31, 2023

morpheus65535 commented Jul 31, 2023

morpheus65535 commented Aug 4, 2023

imthenachoman commented Oct 13, 2023

ChristianMalazarte commented Oct 25, 2023 •

edited

imthenachoman commented Oct 25, 2023

ChristianMalazarte commented Oct 25, 2023

imthenachoman commented Oct 25, 2023

bmorgan99 commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

bmorgan99 commented Feb 2, 2024 •

edited

error: externally-managed-environment: This environment is externally managed #2201

error: externally-managed-environment: This environment is externally managed #2201

Comments

robfantini commented Jul 11, 2023 • edited

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023 • edited

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023

morpheus65535 commented Jul 12, 2023

robfantini commented Jul 12, 2023

morpheus65535 commented Jul 12, 2023

morpheus65535 commented Jul 31, 2023

robfantini commented Jul 31, 2023

morpheus65535 commented Jul 31, 2023

morpheus65535 commented Aug 4, 2023

imthenachoman commented Oct 13, 2023

ChristianMalazarte commented Oct 25, 2023 • edited

imthenachoman commented Oct 25, 2023

ChristianMalazarte commented Oct 25, 2023

imthenachoman commented Oct 25, 2023

bmorgan99 commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

morpheus65535 commented Jan 28, 2024

imthenachoman commented Jan 28, 2024

bmorgan99 commented Feb 2, 2024 • edited

robfantini commented Jul 11, 2023 •

edited

robfantini commented Jul 12, 2023 •

edited

ChristianMalazarte commented Oct 25, 2023 •

edited

bmorgan99 commented Feb 2, 2024 •

edited