How to fix the Docker error for exec user process caused "no such file or directory"
If you've ever received a Docker error for "no such file or directory", this is a possible solution.
standard_init_linux.go:207: exec user process caused "no such file or directory"
Make sure all of the scripts that are being run in the container (this is especially true for
entrypoint.sh) are using a process that exists.
If it is an
entrypoint.sh, you probably need to make sure to do this:
- #!/bin/bash + #!/bin/sh
If you need
bash features, use an Alpine distro with
bash already installed or install it in the
When I'm using Docker and the
alpine linux, I sometimes forget that it doesn't have
bash installed and accidentally add the sha-bang for
#!/bin/bash. 99.9% of the time that's okay, so I change it to
This is especially true when I'm making a GitHub Action.
Hey, I'm Chase. I help aspiring entrepreneurs and makers turn their ideas into digital products and apps.
A figma community project of vectorized hand-drawn arrows.Go To Figma
A figma community project of vectorized hand-drawn lines.Go To Figma
A figma community project of vectorized hand-drawn shapes.Go To Figma
Subscribe to my Newsletter
Every other week I publish the Curiously Crafted newsletter.
In it, I explore the intersection of curiosity and craft: the people who make stuff, what they make and the way they pursue the craft of making.
I'm on almost all social media as @curiouslychase.