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

Question

I am building the Dockerfile for python script which will run in minikube windows 10 system below is my Dockerfile

Building the docker using the below command docker build -t python-helloworld .

and loading that in minikube docker demon docker save python-helloworld | (eval $(minikube docker-env) && docker load)

Docker File

FROM python:3.7-alpine
#add user group and ass user to that group
RUN addgroup -S appgroup && adduser -S appuser -G appgroup

#creates work dir   
WORKDIR /app

#copy python script to the container folder app
COPY helloworld.py /app/helloworld.py

#user is appuser
USER appuser

ENTRYPOINT  ["python", "/app/helloworld.py"]

pythoncronjob.yml file (cron job file)

apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: python-helloworld
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      backoffLimit: 5
      template:
        spec:
          containers:
          - name: python-helloworld
            image: python-helloworld
            imagePullPolicy: IfNotPresent
            command: [/app/helloworld.py]
          restartPolicy: OnFailure

Below is the command to run this Kubernetes job kubectl create -f pythoncronjob.yml

But getting the below error job is not running scuessfully but when u ran the Dockerfile alone its work fine

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

Related: https://stackoverflow.com/questions/42494853/standard-init-linux-go178-exec-user-process-caused-exec-format-error — Ciro Santilli Путлер Капут 六四事, Sep 01 '20 at 14:51

Rufus · Answer 1 · 2020-09-09T15:14:46.183

169

This can also happen when your host machine has a different architecture from your guest container image.

E.g. running an arm container on a host with x86-64 architecture

edited Sep 09 '20 at 15:14

answered Sep 08 '20 at 05:24

Rufus

4,375
3
24
38

6

In my case, I was running x86-64 architecture on Raspberry Pi. Had to change the base image to ARM – mr i.o Jan 15 '21 at 02:29
I was wondering why my docker build fails on CI runner. Thanks! – Shinebayar G Feb 24 '21 at 20:42
9

I got the same thing building on an M1 mac with docker preview for Apple Silicon. My solution was to build on a different device. – Caleb Mar 12 '21 at 21:32
@Caleb Now, that's not really a *solution*, is it? More like a workaround. – Riwen Apr 15 '21 at 08:01
11

That's crazy, this is the main selling point of containerization, docker etc. – Yagiz Degirmenci May 02 '21 at 18:48
6

Oof I wouldn't have thought of that. Damn you M1 processor! – mawburn May 23 '21 at 02:53
Switch a kubernetes cluster node type, without paying attention to the fact that the arch was different – Dennis Jul 03 '21 at 19:00
1

@mawburn I know that feel – afe Jul 28 '21 at 15:40

LinPy · Accepted Answer · 2019-10-09T07:36:38.950

56

I can see that you add the command command: [/app/helloworld.py] to yaml file.

so you need to (in Dockerfile):

RUN chmod +x /app/helloworld.py

set shebang to your py file:

#!/usr/bin/env python # whatever your defualt python to run the script

or setup the command the same as you did in Dockerfile

edited Oct 09 '19 at 07:36

answered Oct 09 '19 at 07:30

LinPy

14,991
3
31
47

2

Thanks @LinPy. I forget this frequently and you're always here to answer. :-) – Josiah Oct 23 '20 at 14:14
I had the same problem trying to run a docker in SageMaker environment. This solution perfectly worked, thanks a lot! – GiulioSanto Sep 15 '21 at 12:12

score 41 · Answer 3 · answered Dec 02 '19 at 10:49

41

I recently encountered the problem when running a logstash container

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

Noticed that the shebang line (#!/bin/sh) on the entrypoint.sh was typed in the second line instead of the first line of the entrypoint.sh file.

When the shebang line is made as to the first line in the script, the error went away and "docker run -it logstashimage:latest sh" worked perfectly.

answered Dec 02 '19 at 10:49

Sajith Kumar Ganesan

525
3
5

Omg it took me almost an hour and I hadn't realized that. Thanks! – Yago Dórea Mar 15 '22 at 19:11
Further explanation https://stackoverflow.com/questions/12910744/why-should-the-shebang-line-always-be-the-first-line – pupher Apr 22 '22 at 19:16

Vincent J · Answer 4 · 2021-10-13T07:25:10.353

30

For those on arm64 (Apple M1 ?) who want to compile for a production use, I managed to make it work with the --platform option of docker build.

docker build --platform linux/amd64 -t registry.gitlab.com/group/project:1.0-amd64 ./

you can, on the other way, choose linux/arm64.

edited Oct 13 '21 at 07:25

answered Sep 21 '21 at 17:24

Vincent J

3,348
1
30
39

2

After days of searching, this solved it for me. `--platform linux/amd64` – toondaey Apr 07 '22 at 10:40
Thank you, Vincent The solution works well. – Nishant Mendiratta May 11 '22 at 18:39

score 11 · Answer 5 · answered Apr 01 '21 at 11:00

I had this issue recently. Sharing my experience here. Basically I was trying to run a ARM docker image on X86_64 architecture.

Here is the steps I have followed

Check host architecture

 uname -m # Display the host architecture
 #x86_64

 docker pull arm32v7/ubuntu # Get ARM docker image

 docker run --rm -t arm32v7/ubuntu uname -m
 standard_init_linux.go:211: exec user process caused "exec format error"

Setting up ARM emulation on x86

Using QEMU allows us to to build ARM binaries on x86 machine without needing a cross compiler.

sudo apt-get install qemu binfmt-support qemu-user-static # Install the qemu packages
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes # This step will execute the registering scripts

Run the docker image

$ docker run --rm -t arm32v7/ubuntu uname -m
armv7l

Reference : Building ARM container on x86

score 8 · Answer 6 · answered Jun 15 '21 at 01:45

8

Rufus is correct, I came across this issue when attempting to build a x86 server image on my M1 MacBook which is arm64.

I was able to build for the correct target architecture by adding the "platform" attribute to my docker-compose.yml.

services:
    web:
        image: myimage/web:latest
        platform: linux/x86_64
        build:
            context: ./myfolder
            dockerfile: Dockerfile.prod

answered Jun 15 '21 at 01:45

Noah Pan

81
1
1

This solved my issue with docker compose, however note that it only worked with the newer `docker compose` vs. `docker-compose`. The new `docker compose` is a drop in replacement and I had no issues doing just that. – Erebus Jan 13 '22 at 23:00
You just saved my life. After 1.5 days of pulling my hair out as to why my new Mac can't spin up the same AWS ECS container using exactly the same code as my old Mac, and after getting no error logs from AWS. This, after pulling an error log from the Celery container on my AWS instance via SSH that gave a me new Google search term to use that ultimately led me to this page and your comment, was the answer. I thank you :). – N.Widds Mar 22 '22 at 16:01

score 7 · Answer 7 · answered Jan 03 '20 at 18:34

7

Another two reasons could raise this issue if you run docker on Windows:

scripts line endings are not LF (linux)
scripts encoding should be utf-8 + BOM

answered Jan 03 '20 at 18:34

DennisKot

87
1
1

score -1 · Answer 8 · answered Mar 30 '21 at 10:33

-1

I met exactly the same error message. It was fixed by install qemu on the host machine. No idea about the reason.

answered Mar 30 '21 at 10:33

fishautumn

334
2
6

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

8 Answers8

Linked

Related