-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
start panic #27940
Comments
ping @mlaventure |
I would need more detail if possible:
|
I've got this mystery as well, and very little relevant debugging experience (daemon logs?).
|
You should be able to get the docker daemon logs via: If you could also specify which command resulted in this panic, it'll be helpful. Thanks! |
I'm able to get into the image if I override my ENTRYPOINT script. Here are the last several lines of output from the daemon logs:
|
@conversica-aaronpa You still haven't provided what command(s) lead to this panic 😅 |
Example of how I'm seeing what I think is the same problem:
Content of the Dockerfile entrypoint scripts:
and
Image made with this Dockerfile
|
I think the problem as I'm experiencing it may be related to Windows (CRLF) vs Linux (LF) line endings in my entrypoint script. Changing to Linux style (didn't mean to go to Windows at all) seems to have resolved my problem. |
Oh, I see. It makes sense. Linux doesn't know how to take care of This PR removed the panic. |
I am able to reproduce this without involving any fancy new line endings. This leads me to believe that the problem is general and is not limited to use case of @conversica-aaronpa. I have a very simple script
which has its executable flag set. Then the familiar panic happens when trying to execute it in a container:
System Information My docker info:
I am running this on OSX 10.11.6. I've also tested the same thing on docker 1.12.1 running on CentOS 7.2.1511 and the result is the same. |
/cc @justincormack |
@ironsmile This is because alpine doesn't contain The actual panic was removed in opencontainers/runc#1117 which now just returns an error instead of panicing. I'm going to close this since it looks like a non-issue. |
* array format for ENTRYPOINT is required if using CMD arguments * alpine is causing a container stack strace: based on moby/moby#27940 this would mean there is some alpine pkg I need installed but I don't know what
Which part of the system is depending on My Go application was working in Alpine just fine, until today, when I see these weird error traces. Update Turns out I accidentally placed a GNU libc binary onto an Alpine (musl) image. Would have been nice to get a more direct error message when this happens. |
@mcandre Nothing in docker relies on @cyberbeast Not sure why you thumbs-downed my comment |
The text was updated successfully, but these errors were encountered: