1

Created docker file and image successfully build and contained is also created but status is exited.

Staus Exited in "docker ps -a"

Receiving an error while accessing the Docker and check logs also

standard_init_linux.go:175: exec user process caused "no such file or directory"

Below are the details of file: Dockerfile and command

Docker File:

Docker File Detail

Docker Command detail and error

Docker Command Deails

  • No need to delete a question and recreate a new one to update it. Anyway, it looks like the issue comes from entrypoint.sh or start.sh if I'm not mistaken. Possible to post their content here? – David B. Oct 27 '16 at 12:06
  • start.sh: #!/bin/bash # start all the services supervisord -n Enterypoint.sh: #!/bin/bash set -e exec "$@" – Nayan Vanza Oct 28 '16 at 5:26
2

The container for your lamp image shows "/entrypoint.sh /bin/" as command, which fails.

I would update your ENTRYPOINT line in your Dockerfile to:

ENTRYPOINT ["/bin/bash", "/entrypoint.sh"] as you did with CMD, build the image and run it again.

0

I experienced a similar issue. In my case it was because I was building my image on a windows machine. Windows adds "hidden characters" to files such as entrypoint.sh. To remove these characters you can run this command on the entrypoint.sh file after copying it into your container:

COPY entrypoint.sh /usr/local/bin/
RUN dos2unix /usr/local/bin/entrypoint.sh

now rebuild the image and try again. This solution worked for me.

You can read more about this anomaly here:

https://www.liquidweb.com/kb/dos2unix-removing-hidden-windows-characters-from-files/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.