Skip to content
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

Upgrade to Alpine 3.19 breaks build #17

Open
deltaGPhys opened this issue Feb 27, 2024 · 1 comment
Open

Upgrade to Alpine 3.19 breaks build #17

deltaGPhys opened this issue Feb 27, 2024 · 1 comment

Comments

@deltaGPhys
Copy link

The upgrade last month to Alpine 3.19 seems to be causing this error in my build. Docker Hub doesn't appear to show a tag other than latest. Is there any way for me to use the previous version?

Thanks!

[2024-02-27 00:22:22] │ INFO[0047] Running: [/bin/sh -c pip install -r requirements.txt] 
[2024-02-27 00:22:24] │ INFO[0049] Pushed <registry-uri-7> 
[2024-02-27 00:22:25] │ error: externally-managed-environment
[2024-02-27 00:22:25] │ 
[2024-02-27 00:22:25] │ × This environment is externally managed
[2024-02-27 00:22:25] │ ╰─> 
[2024-02-27 00:22:25] │     The system-wide python installation should be maintained using the system
[2024-02-27 00:22:25] │     package manager (apk) only.
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     If the package in question is not packaged already (and hence installable via
[2024-02-27 00:22:25] │     "apk add py3-somepackage"), please consider installing it inside a virtual
[2024-02-27 00:22:25] │     environment, e.g.:
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     python3 -m venv /path/to/venv
[2024-02-27 00:22:25] │     . /path/to/venv/bin/activate
[2024-02-27 00:22:25] │     pip install mypackage
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     To exit the virtual environment, run:
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     deactivate
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     The virtual environment is not deleted, and can be re-entered by re-sourcing
[2024-02-27 00:22:25] │     the activate file.
[2024-02-27 00:22:25] │     
[2024-02-27 00:22:25] │     To automatically manage virtual environments, consider using pipx (from the
[2024-02-27 00:22:25] │     pipx package).
[2024-02-27 00:22:25] │ 
[2024-02-27 00:22:25] │ 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.
[2024-02-27 00:22:25] │ hint: See PEP 668 for the detailed specification.
[2024-02-27 00:22:25] │ 
[2024-02-27 00:22:25] │ [notice] A new release of pip is available: 23.3.2 -> 24.0
[2024-02-27 00:22:25] │ [notice] To update, run: pip install --upgrade pip
[2024-02-27 00:22:25] │ error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1
[2024-02-27 00:22:25] │ 
[2024-02-27 00:22:25] │ command exited with code 1
@frol
Copy link
Member

frol commented Feb 27, 2024

@deltaGPhys Double-check that you use the latest image as I have explicitly disabled the EXTERNALLY-MANAGED flag.

I cannot reproduce your issue:

image

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

No branches or pull requests

2 participants