-
Notifications
You must be signed in to change notification settings - Fork 81
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
Can't run container #12
Comments
Follow-up: building the image on Windows creates the issue. Probably a CRLF/LF conversion when I cloned the repository... |
Thanks for the report and self diagnosis! |
same issue on Mac OS Mojave |
Hello @umutc ! I am Greg from NGINX Inc. I will be assisting you with this issue going forward. The message you are seeing seems to be caused by either lack of shebang (the #!/bin/bash in first line of your script) or invalid file encoding. Could you try run your Dockerfile and entrypoint script through utility called dos2unix that does CRLF (windows style line endings) conversion to LF (UNIX style line endings) and then retry your build? Sincerely, |
Hi, I'm trying to use Amplify and followed the README on how to create the container and run the image. Unfortunately, the container exist immediately and the only information from the logs are is standard_init_linux.go:185: exec user process caused "no such file or directory".
Any help on how to solve this? I built the image from the current master branch.
Regards,
Fabian
The text was updated successfully, but these errors were encountered: