Docker Error3 Fixes Available

standard_init_linux.go: exec user process caused "exec format error"

standard_init_linux.go:211: exec user process caused "exec format error"

What does this error mean?

This cryptic error usually means you are trying to run a binary or container built for a different CPU architecture than the one you are running on. Most commonly, it happens when running an 'linux/amd64' (Intel) container on an 'linux/arm64' (Apple Silicon) machine, or vice versa, without emulation.

Common Causes

Building a Docker image on an M1 Mac (arm64) and trying to run it on an Intel server (amd64)
The shell script entrypoint is missing the shebang line (#!/bin/sh)
The entrypoint script was saved with Windows line endings (CRLF) instead of Linux (LF)
The binary inside the container is not compatible with the container's OS

How to Fix It (3 Solutions)

Build with --platform flag

Explicitly specify the target platform when building or pulling.

Code

# Build for Intel/AMD64 (standard servers) regardless of your machine
docker build --platform linux/amd64 -t my-image .

# Run with platform flag
docker run --platform linux/amd64 my-image

Fix line endings in entrypoint scripts

If your entrypoint is a shell script, ensure it has LF (Linux) line endings, not CRLF (Windows).

Code

# Convert CRLF to LF using sed
sed -i 's/
$//' entrypoint.sh

Check the shebang line

Ensure your script starts with #!/bin/sh or #!/bin/bash.

Code

#!/bin/sh
# The rest of your script...

Fix this error faster with our free tool

Chmod Calculator (Fix Script Permissions)

Open Chmod Calculator (Fix Script Permissions)

Related Errors

Linux

bash: Permission denied

View fix

Docker

Docker: Bind for 0.0.0.0:PORT failed — port is already allocated

View fix

Docker

Error: Bind for 0.0.0.0:PORT failed — port is already allocated

View fix

Browse all error fixes