panic: spanic: standard_init_linux.go:178: exec user process caused "no such file or directory"red] /usr/local/go/src/runtime/panic.go:481 +0x3e6 github.com/urfave/cli.HandleAction.func1(0xc8201092e8) panic(0x/tmp/tmp.SspaUm6Eju/src/github.com/opencontainers/runc/Godeps/_workspace/src/github.com/…

your suggestions are appreciated if you come across these kind of errors

Hi, I got similar problem :frowning: panic: standard_init_linux.go:178: exec user process caused “no such file or directory” [recovered] panic: standard_init_linux.go:178: exec user process caused “no such file or directory” […]

Solved :slight_smile: In the Dockerfile check if in the Entrypoint you start some script. If you start these script be sure that the first line is: #!/bin/sh Instead of: #!/bin/bash A greeting.

Awesome! Changing script to point to sh instead of bash fixed my issue!

I also got into same trouble. In my case, modifying bash is not solved either.

I ran into the same issue. In my case I used a docker host on Windows, and my entry point script contained the well know windows end-of-line characters (^M). As /bin/bash^M cannot be found. Simply removed these lines (dos2unix in windows powershell will help you).

Thanks for reply. although I have set “set ff=unix” in vim, but It still not working. but It is certain that there is a problem with entry point script. if exclude entry point script, it work well.

You can run the image just before running the endpoint interactively, and then run the entrypoint manually. You will can then more easily debug the entrypoint issue. Something like: add ^M to scripts to showcase problem: PS D:\peter\git\docker-nginx-ssl-secure> unix2dos .\ entrypoint.sh unix2do…

This post made me realise my issue was line endings on windows for a similar error output. Thanks so much!

Getting panic: spanic: standard_init_linux.go:178: exec user process caused "no such file or directory"red] while running the docker image

Docker Desktop

dbinary (dbinary) January 29, 2017, 12:30pm 7

Try to posting a sample code that reproduces the error, Dockerfile and/or script started at Entrypoint.
I’m not an expert but maybe someone know more about the trouble.

A greeting.

Topic		Replies	Views
Standard_init_linux.go:175 exec user process caused no such file General	20	183770	May 4, 2020
Standard_init_linux.go:187: exec user process caused "no such file or directory" General	5	29565	July 2, 2019
Exec user proccess caused "no such file or directory" General	2	10108	July 10, 2019
Weird error, "exec /docker-entrypoint.sh: no such file or directory" but the file is there?!? General	1	8028	May 15, 2025
Standard_init_linux.go:175: exec user process caused "no such file or directory" General	1	2673	October 13, 2016

Getting panic: spanic: standard_init_linux.go:178: exec user process caused "no such file or directory"red] while running the docker image

Related topics