-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Missing dependencies when using python:3 #305
Comments
I have a test.
It can install successfuly by pip. And I install Pillow by source code.
I got the seem issue. But, let's look at the installed packages.
The Pillow's The actual path is
The source code https://github.com/python-pillow/Pillow/blob/5.2.x/setup.py#L452 return True, but next line reture None. So, https://github.com/python-pillow/Pillow/blob/5.2.x/setup.py#L582 raised. |
Yes, some symlinks (eg Edit: I think that the problem is caused by this commit debuerreotype/docker-debian-artifacts@a6d5897. |
Yes, so it's not the image's issue, |
I agree. Probably is more related to Pillow (because of |
So I'm closing this issue. |
Answering the question: Pillow needs |
As far as the missing symlink for $ docker run --rm python:3.7-stretch dpkg -l | grep zlib
ii zlib1g:amd64 1:1.2.8.dfsg-5 amd64 compression library - runtime
ii zlib1g-dev:amd64 1:1.2.8.dfsg-5 amd64 compression library - development
$ docker run --rm python:3.6-stretch dpkg -l | grep zlib
ii zlib1g:amd64 1:1.2.8.dfsg-5 amd64 compression library - runtime
ii zlib1g-dev:amd64 1:1.2.8.dfsg-5 amd64 compression library - development |
Glad that you fixed! About the symlink, it was my mistake. I was looking for it on the wrong directories, but Can I ask you what about docker-library/php#556 do you plan to do? Save the list of packages installed on previous stages, install what is needed for the build and then autoremove them. There is something about it that I missed? As curiosity, do you know if can be assumed that if |
I keep my images with the tag
python:3
because Python versioning says that 3.x are always compatible with previous 3.x versions. However latest update on tagpython:3
(that now is3.7.0-stretch
) causes build failures on my requirements.txt.Because of this 3.7 was not ready to leave rc.
The workaround is simply change base image from
python:3
topython:3.6
.The text was updated successfully, but these errors were encountered: