Skip to content

prevent RUN pip3 install build error #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

diranetafen
Copy link

prevent this build error by using working alpine image without update application code

#8 [4/7] RUN pip3 install --no-cache-dir -q -r /tmp/requirements.txt #8 2.007 error: externally-managed-environment
#8 2.007
#8 2.007 �� This environment is externally managed #8 2.007 ������>
#8 2.007 The system-wide python installation should be maintained using the system
#8 2.007 package manager (apk) only.
#8 2.007
#8 2.007 If the package in question is not packaged already (and hence installable via
#8 2.007 "apk add py3-somepackage"), please consider installing it inside a virtual
#8 2.007 environment, e.g.:
#8 2.007
#8 2.007 python3 -m venv /path/to/venv
#8 2.007 . /path/to/venv/bin/activate
#8 2.007 pip install mypackage
#8 2.007
#8 2.007 To exit the virtual environment, run:
#8 2.007
#8 2.007 deactivate
#8 2.007
#8 2.007 The virtual environment is not deleted, and can be re-entered by re-sourcing
#8 2.007 the activate file.
#8 2.007
#8 2.007 To automatically manage virtual environments, consider using pipx (from the
#8 2.007 pipx package).
#8 2.007
#8 2.007 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.
#8 2.007 hint: See PEP 668 for the detailed specification.
#8 ERROR: process "/bin/sh -c pip3 install --no-cache-dir -q -r /tmp/requirements.txt" did not complete successfully: exit code: 1

…ailed

heroku#8 [4/7] RUN pip3 install --no-cache-dir -q -r /tmp/requirements.txt
heroku#8 2.007 error: externally-managed-environment
heroku#8 2.007 
heroku#8 2.007 �� This environment is externally managed
heroku#8 2.007 ������> 
heroku#8 2.007     The system-wide python installation should be maintained using the system
heroku#8 2.007     package manager (apk) only.
heroku#8 2.007     
heroku#8 2.007     If the package in question is not packaged already (and hence installable via
heroku#8 2.007     "apk add py3-somepackage"), please consider installing it inside a virtual
heroku#8 2.007     environment, e.g.:
heroku#8 2.007     
heroku#8 2.007     python3 -m venv /path/to/venv
heroku#8 2.007     . /path/to/venv/bin/activate
heroku#8 2.007     pip install mypackage
heroku#8 2.007     
heroku#8 2.007     To exit the virtual environment, run:
heroku#8 2.007     
heroku#8 2.007     deactivate
heroku#8 2.007     
heroku#8 2.007     The virtual environment is not deleted, and can be re-entered by re-sourcing
heroku#8 2.007     the activate file.
heroku#8 2.007     
heroku#8 2.007     To automatically manage virtual environments, consider using pipx (from the
heroku#8 2.007     pipx package).
heroku#8 2.007 
heroku#8 2.007 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.
heroku#8 2.007 hint: See PEP 668 for the detailed specification.
heroku#8 ERROR: process "/bin/sh -c pip3 install --no-cache-dir -q -r /tmp/requirements.txt" did not complete successfully: exit code: 1
Copy link

@yassine-bouassida yassine-bouassida left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants