-
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
The Problem with python:3.6-alpine #378
Comments
The bug is from alpine 3.9 |
Can you provide a minimal reproducer for your issue? (just the error message doesn't really help a whole lot in this case -- the best we can do is guess, which is where the suggestion of https://bugs.alpinelinux.org/issues/9959 comes from) |
This is the first version of my docker file. So before demonstrating it I've build it in my local machine on 01.02.2019. it worked. But when my students tried to build it. (20 laptops) all of them failed. I've removed all images and tried to rebuild it. then got the same error. googled it, and found that it's ordering problem. and then found a commit where that order was changed. Once I've changed the version (just have selected previous version of from docker hub) everyone in my class and me have built and run. ( so you can just copy docker config above and try to build it. I think will find that errors and more details if my is not enough))) |
That's not exactly minimal. 😅
Any chance you could "code golf" that down to something smaller that can
still reproduce the failure to help narrow down what's going wrong?
|
The big things that stand out to me are the Alpine 3.8 mirrors that almost definitely will break on an Alpine 3.9 based image (especially with the transition on system packages from libressl back to openssl); and then the installation of |
I have same problem. The most confused is, when I retry it at alpine`s sh in container. When I splite this cmd to four cmd, and run.every thing is ok.
But run at one line, it will give this error.
... What happen? And it not depends on image of python. Image of 3 weeks ago and image of 4 days ago have same problem. PS: Image of 3 weeks ago: (bb1ccaa5880c). Image of 4 days ago:(f8aff02aba66) Is this is apk`s problem? Proposed the same reply. #9947 |
all right, it isn't every thing ok.
dockerfile:
requirements:(name is : mabopython_requirements.txt)
|
@ziserendexin, First off, that Dockerfile shouldn't work since |
For further help debugging your |
(Closed since the original issue was resolved in #378 (comment), and turned out to be user error.) |
About the origin image, it's the Alpine 3.9.
|
According to your suggestion, he is working properly.Thanks a lot. change to /alpine/v3.9/main, it helpful.
Embarrassing mistake. Orz.... |
thanks a lot, i encounter the same question |
Hi, sorry to post on a closed topic but I ran into a similar issue with grpc. Is this similar? I do apologize, I do not understand what the fix is. Use python:3.9-alpine and add the mirrors? |
Hi. I'm teacher at the university and with students found a problem:
FROM python:3.6-alpine
This is the first line in my DockerFile for our class project. I've successfully build & run it 9 days ago (01.02.2019), but today (09.02.2019) no one has build built it (+20 students).
So I've removed that image in my local machine and tried to built it and got the same error as everyone in my class:
Error relocating /usr/local/lib/libpython3.6m.so.1.0: getrandom: symbol not found ERROR: Service 'django' failed to build: The command '/bin/sh -c pip install -r /requirements/local.txt' returned a non-zero code: 127
So we did a little research and found that the last changes has been done 3 days ago (06.02.2019)
commit and I think that is the reason of our failures.
I've changed it to
FROM python:3.6.8-alpine3.8
and everyone has build it successfully.Thanks.
The text was updated successfully, but these errors were encountered: