-
Notifications
You must be signed in to change notification settings - Fork 18
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
Proper way to install Proj with Python bindings with Debian Bookworm base image #21
Comments
Ok, found out: First
This can be fixed by setting the ENV var Then next this warning:
This can be fixed by setting the ENV var So now only
|
justb4
added a commit
to justb4/docker-mapproxy
that referenced
this issue
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This concerns https://github.com/justb4/docker-mapproxy/blob/master/Dockerfile (my fork). The Dockerfile installs both
python3-proj
and the PyPi packagepyproj
. Think I first addedpython3-proj
and thenpyproj
later as for some build errors. My question arises, since I think one gets two full and even different versions installed at different locations/usr/
(python3-proj
) and/usr/local
(pyproj
).I was triggered by this warning:
"Bashing" into that running MapProxy image I see:
And (the default)
The latter is the default:
Setting an Env var for the Docker Container
PROJ_DATA= /usr/local/lib/python3.11/site-packages/pyproj/proj_dir/share/proj
clears the error message (see above), but it all feels brittle.The PyPi version
pyproj
also is more recent. Can I assume that we could leave outpython3-proj
? Or do we have to install alibproj-dev
?The text was updated successfully, but these errors were encountered: