Docker Error: standard_init_linux.go:175: exec user process caused “no such file or directory” – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, docker, , , .
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 Command detail and error
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.
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: