standard init linux go 190 exec user process caused no such file or directory - Docker

Question

When I am running my docker image on windows 10  I am getting this error   standard init linux go 190  exec user process caused  no such file or directory    my docker file is   FROM openjdk 8  EXPOSE 8080  VOLUME  tmp  ADD appagent tar gz  opt app-agent ADD services jar app jar ADD run sh  run sh    Install compiler and perl stuff RUN apt-get update RUN apt-get install -y build-essential RUN apt-get install -y gcc-multilib RUN apt-get install -y perl    Install Percona Toolkit RUN apt-get install --yes percona-toolkit RUN   chmod     x     run sh   ENTRYPOINT    run sh     and the script is start with    bin sh     bin sh set -e  JAVA OPTS  -Dfile encoding UTF-8 -Djava security egd file  dev urandom   if      APPD APP NAME            then JAVA AGENT  -javaagent  opt app-agent javaagent jar fi  exec java   JVM OPTS    JAVA OPTS    JAVA AGENT  -jar  app jar   Tried method1  Tried changing    bin sh to    bin bash but getting same error   Tried method2  added dos2unix in docker file  RUN apt-get install -y dos2unix RUN dos2unix  run sh

User · Accepted Answer

Use notepad    go to edit -  EOL conversion -  change from CRLF to LF

User · Answer

I had the same issue when using the alpine image   My  sh file had the following first line      bin bash   Alpine does not have bash  So changing the line to     bin sh   or installing bash with  apk add --no-cache bash   solved the issue for me

User · Answer

This is because the shell script is formatted in windows we need to change to unix format  You can run the dos2unix command on any Linux system  dos2unix your-file sh  If you don   t have access to a Linux system  you may use the Git Bash for Windows which comes with a dos2unix exe dos2unix exe your-file sh

User · Answer

No such file or directory  is coming from Linux  and I ve seen the following causes   First cause is not actually having the file inside your container  Some people try to run a command from the host without adding it to their image  Some people shadow their command by mounting a volume on top of the command they wanted to run  If you run the same container  but with a shell instead of your normal entrypoint cmd value  and run an ls  path to cmd you ll see if this exists   The next cause is running the wrong command  This often appears with json exec formatting of the command to run that doesn t parse correctly  If you see a command trying to run   app   or something similar  the json string wasn t parsed by Docker and Linux is trying to use a shell to parse the command as a string  This can also happen if you misorder the args  e g  trying to run -it is a sign you tried to place flags after the image name when they must be placed before the image name   With shell scripts  this error appears if the first line with the    points to a command that doesn t exist inside the container  For some  this is trying to run bash in an image that only has  bin sh  And in your case  this can be from Windows linefeeds in the script  Switching to Linux Unix linefeeds in your editor will correct that   With binaries  this error appears if a linked library is missing  I ve seen this often when Go commands that are compiled with libc  but run on alpine with musl or scratch without any libraries at all  You need to either include all the missing libraries or statically compile your command  To see these library links  use ldd  your app on your binary

User · Answer

Note a similar error such as  standard init linux go 211  exec user process caused  quot no such file or directory quot   can happen if the architecture an image was built for does not match the one of your system  For instance  trying to run an image built for arm64 on a x86 64 machine can generate this error

User · Answer

I solve this issue set my settings in vscode    File   Preferences   Settings   Text Editor   Files Eol - set to  n       Regards

User · Answer

Suppose you face this issue while running your go binary with in alpine container   Export the following variable before building your bin    CGO has to be disabled for alpine export CGO ENABLED 0   Then go build

User · Answer

Replacing CRLF with LF using Notepad     Notepad   s Find Replace feature handles this requirement quite nicely  Simply bring up the Replace dialogue  CTRL H   select Extended search mode  ALT X   search for     r n    and replace with     n      Hit Replace All  ALT A    Rebuild and run the docker image should solve your problem

User · Answer

I found a particular edge case where I was using the tini init in an alpine container  but since I was not using the statically linked version  and Alpine uses musl libc rather than GNU LibC library installed by default  it was crashing with the very same error message  Had I understood this and also taken time to read the documentation properly  I would have found Tini Static  which upon changing to  resolved my problem

User · Answer

in my case I had to change line ending from CRLF to LF for the run sh file and the error was gone   I hope this helps  Kirsten

User · Answer

Add this to your Dockerfile  RUN cat  run sh   tr -d   r   gt   run sh

User · Answer

I m unable to comment due to my rep  but I just wanted to add  for VSCode users  you can change CRLF line endings to LF by clicking on CRLF in the status bar  then select LF and save the file   I had the same issue  and this resolved it

User · Answer

It s a CRLF problem  I fixed the problem using this    git config --global core eol lf  git config --global core autocrlf input  find   -type f -print0   xargs -0 dos2unix

User · Answer

There are multiple right answers here  I don t see the VIM version of it so here it is  Open your file in VIM  check the bottom status line for example  execute set ff dos  for CRLF  or set ff unix  for LF

User · Answer

change entry point as below  It  worked for me  ENTRYPOINT   sh    run sh     As tuomastik pointed out in the comments  the docs require the first parameter to be the executable      ENTRYPOINT has two forms       ENTRYPOINT   executable    param1    param2    exec form  preferred       ENTRYPOINT command param1 param2  shell form

[docker] standard_init_linux.go:190: exec user process caused "no such file or directory" - Docker

Examples related to docker

Examples related to dockerfile

Examples related to docker-for-windows