-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Entrypoint script not working even though present. #22779
Comments
Please run The log file should tell us more what exactly is missing. |
Ran
|
strange, your reproducer works fine for me on linux as well. The strace doesn't show us much more either other than it cannot find Do you store you files with windows line endings? I think it is possible that you entrypoint file has CR+LF windows line endings instead of LF linux line endings, as such the shebang which is execute when the script is loaded is not the normal |
No carriage returns in |
Did you run something like |
Interesting. I think I understand what is happening. I did the check in my linux vm and there I have LF endings but the container I built from Windows I have CR+LF endings.
The reason seems to be the autocrlf feature of git. It changed line endings and then the shebang of my entrypoint script broke.
Turning off gits autocrlf so called feature with Thank you for your time! Sorry that the issue wasn't related to podman. |
Issue Description
The following error is thrown when trying to start container.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The container would not start.
Describe the results you expected
Expected the container to start.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Using Podman Desktop on Windows 10 Enterprise, 22H2.
Additional information
The text was updated successfully, but these errors were encountered: