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

Docker error "We have switched from .json to .py" #325

Open
pinkairfreshener opened this issue Mar 23, 2024 · 3 comments
Open

Docker error "We have switched from .json to .py" #325

pinkairfreshener opened this issue Mar 23, 2024 · 3 comments

Comments

@pinkairfreshener
Copy link

"We have switched from .json to .py for config to have a much more lenient experience
Looks like the auto updater didnt work though
Updating is just 2 easy steps:
1: Rename /Upload-Assistant/data/config.json to /Upload-Assistant/data/config.py
2: Add config = to the beginning of /Upload-Assistant/data/config.py"

Using the latest edition of ghcr.io/l4gsp1ke/upload-assistant:master via docker compose.

Also, I am using a config.py file with config = at teh top so not sure what I need to do to get this to work. Thanks.

@basings
Copy link

basings commented Mar 30, 2024

I've got the same issue.

I tried building the Dockerfile with podman locally in order to see what's going on but it fails at using pip3.

(136/136) Installing python3-dev (3.11.8-r0)
Executing busybox-1.36.1-r15.trigger
Executing ca-certificates-20240226-r0.trigger
Executing glib-2.78.4-r0.trigger
OK: 1452 MiB in 169 packages
--> 3a44ec00f4ea
STEP 4/9: RUN pip3 install wheel
error: externally-managed-environment

× This environment is externally managed
╰─> 
    The system-wide python installation should be maintained using the system
    package manager (apk) only.
    
    If the package in question is not packaged already (and hence installable via
    "apk add py3-somepackage"), please consider installing it inside a virtual
    environment, e.g.:
    
    python3 -m venv /path/to/venv
    . /path/to/venv/bin/activate
    pip install mypackage
    
    To exit the virtual environment, run:
    
    deactivate
    
    The virtual environment is not deleted, and can be re-entered by re-sourcing
    the activate file.
    
    To automatically manage virtual environments, consider using pipx (from the
    pipx package).

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.
Error: building at STEP "RUN pip3 install wheel": while running runtime: exit status 1

@basings
Copy link

basings commented Mar 30, 2024

Using the image FROM python:3-alpine instead of base alpine solves that issue

edit: yet it can't import data/config.py which is why it fails.

@mkdew37
Copy link

mkdew37 commented Sep 30, 2024

Have the same issue. Everything it says in the steps I have already. Did anyone find a solution?

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

3 participants