[GH-ISSUE #298] standard_init_linux.go:211: exec user process caused "exec format error" #262

Closed
opened 2026-02-26 06:31:49 +03:00 by kerem · 17 comments
Owner

Originally created by @talondnb on GitHub (Feb 20, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/298

image: jc21/nginx-proxy-manager:latest

Describe the bug
npm app doesn't boot, with the logs showing:
standard_init_linux.go:211: exec user process caused "exec format error"

To Reproduce
docker-compose.yaml (previously worked fine until recent update)

version: "3.5"

volumes:
  data:
    driver: local
    driver_opts:
      type: nfs4
      o: addr=10.10.10.100,rw,noatime,rsize=8192,wsize=8192,tcp,timeo=14
      device: ":/volume1/Config/npm/data"
  letsencrypt:
    driver: local
    driver_opts:
      type: nfs4
      o: addr=10.10.10.100,rw,noatime,rsize=8192,wsize=8192,tcp,timeo=14
      device: ":/volume1/Config/npm/letsencrypt"

services:
  app:
    image: jc21/nginx-proxy-manager:latest
    restart: always
    ports:
      - "80:80"
      - "443:443"
      - "81:81"
    volumes:
      # Make sure this config.json file exists
      - /mnt/config/npm/config.json:/app/config/production.json
      - data:/data
      - letsencrypt:/etc/letsencrypt
    depends_on:
      - db
  db:
    image: yobasystems/alpine-mariadb:latest
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: "npm"
      MYSQL_DATABASE: "npm"
      MYSQL_USER: "npm"
      MYSQL_PASSWORD: "password"
    volumes:
      # Does not work on an NFS volume
      - /home/xxx/npm/data/mysql:/var/lib/mysql

Expected behavior
npm app boots normally

Operating System
Hypriot docker image on Pi4

Originally created by @talondnb on GitHub (Feb 20, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/298 image: jc21/nginx-proxy-manager:latest **Describe the bug** npm app doesn't boot, with the logs showing: standard_init_linux.go:211: exec user process caused "exec format error" **To Reproduce** docker-compose.yaml (previously worked fine until recent update) ``` version: "3.5" volumes: data: driver: local driver_opts: type: nfs4 o: addr=10.10.10.100,rw,noatime,rsize=8192,wsize=8192,tcp,timeo=14 device: ":/volume1/Config/npm/data" letsencrypt: driver: local driver_opts: type: nfs4 o: addr=10.10.10.100,rw,noatime,rsize=8192,wsize=8192,tcp,timeo=14 device: ":/volume1/Config/npm/letsencrypt" services: app: image: jc21/nginx-proxy-manager:latest restart: always ports: - "80:80" - "443:443" - "81:81" volumes: # Make sure this config.json file exists - /mnt/config/npm/config.json:/app/config/production.json - data:/data - letsencrypt:/etc/letsencrypt depends_on: - db db: image: yobasystems/alpine-mariadb:latest restart: always environment: MYSQL_ROOT_PASSWORD: "npm" MYSQL_DATABASE: "npm" MYSQL_USER: "npm" MYSQL_PASSWORD: "password" volumes: # Does not work on an NFS volume - /home/xxx/npm/data/mysql:/var/lib/mysql ``` **Expected behavior** npm app boots normally **Operating System** Hypriot docker image on Pi4
kerem 2026-02-26 06:31:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

This seems to be because of the latest multi arch build, perhaps not using the right one for my Pi 4.

<!-- gh-comment-id:588998103 --> @talondnb commented on GitHub (Feb 20, 2020): This seems to be because of the latest multi arch build, perhaps not using the right one for my Pi 4.
Author
Owner

@jc21 commented on GitHub (Feb 20, 2020):

I don’t have a pi 4 yet, but I’ll take a look at it tomorrow

<!-- gh-comment-id:588998989 --> @jc21 commented on GitHub (Feb 20, 2020): I don’t have a pi 4 yet, but I’ll take a look at it tomorrow
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

Thanks. Pi 4 will be an arm7 build. Can I manually specify somehow?

<!-- gh-comment-id:588999578 --> @talondnb commented on GitHub (Feb 20, 2020): Thanks. Pi 4 will be an arm7 build. Can I manually specify somehow?
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

I've tried latest-arm7l as per tags here:

https://hub.docker.com/r/jc21/nginx-proxy-manager

This doesn't seem to work, no valid dockerfile.

<!-- gh-comment-id:589003672 --> @talondnb commented on GitHub (Feb 20, 2020): I've tried latest-arm7l as per tags here: https://hub.docker.com/r/jc21/nginx-proxy-manager This doesn't seem to work, no valid dockerfile.
Author
Owner

@jc21 commented on GitHub (Feb 20, 2020):

Could you run ‘uname -a’ in you terminal and paste the output. Should tell me the arch and whether it’s 32 or 64 bit

<!-- gh-comment-id:589006002 --> @jc21 commented on GitHub (Feb 20, 2020): Could you run ‘uname -a’ in you terminal and paste the output. Should tell me the arch and whether it’s 32 or 64 bit
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

Linux gliesedocker 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux

<!-- gh-comment-id:589006230 --> @talondnb commented on GitHub (Feb 20, 2020): Linux gliesedocker 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

I suspect you've fixed something as i've just retried the :latest-armv7l tag and it's now working. :)

<!-- gh-comment-id:589009408 --> @talondnb commented on GitHub (Feb 20, 2020): I suspect you've fixed something as i've just retried the :latest-armv7l tag and it's now working. :)
Author
Owner

@jc21 commented on GitHub (Feb 20, 2020):

I thought pi4 was armv8/arm64. A quick look at Hypriot doesn’t seem to offer different versions for Pi 2/3/4

<!-- gh-comment-id:589010410 --> @jc21 commented on GitHub (Feb 20, 2020): I thought pi4 was armv8/arm64. A quick look at Hypriot doesn’t seem to offer different versions for Pi 2/3/4
Author
Owner

@jc21 commented on GitHub (Feb 20, 2020):

By the way, that latest-armv7l tag is not version NPM 2.1.0, its the previous docker manifest version

<!-- gh-comment-id:589011002 --> @jc21 commented on GitHub (Feb 20, 2020): By the way, that latest-armv7l tag is not version NPM 2.1.0, its the previous docker manifest version
Author
Owner

@talondnb commented on GitHub (Feb 20, 2020):

Ahh I see. I’ll await updates before trying the latest tag again. 👍🏼

<!-- gh-comment-id:589011848 --> @talondnb commented on GitHub (Feb 20, 2020): Ahh I see. I’ll await updates before trying the latest tag again. 👍🏼
Author
Owner

@jc21 commented on GitHub (Feb 21, 2020):

Looks like the docker buildx isn't building for the correct architectures. Still looking in to it.

<!-- gh-comment-id:589433983 --> @jc21 commented on GitHub (Feb 21, 2020): Looks like the docker buildx isn't building for the correct architectures. Still looking in to it.
Author
Owner

@jc21 commented on GitHub (Feb 21, 2020):

Nope buildx was working as expected. The real problem is s6-overlay, I've mistakenly been using amd64 binaries for it across all architectures. Rookie move.

<!-- gh-comment-id:589439282 --> @jc21 commented on GitHub (Feb 21, 2020): Nope buildx was working as expected. The real problem is s6-overlay, I've mistakenly been using amd64 binaries for it across all architectures. Rookie move.
Author
Owner

@talondnb commented on GitHub (Feb 21, 2020):

Ah appreciate it, thanks for looking into this promptly.

<!-- gh-comment-id:589446518 --> @talondnb commented on GitHub (Feb 21, 2020): Ah appreciate it, thanks for looking into this promptly.
Author
Owner

@jc21 commented on GitHub (Feb 21, 2020):

All done, pull either latest, 2 or 2.1.1 docker image tag. Tested with arm64 and rpi3 w/ hypriot

<!-- gh-comment-id:589471371 --> @jc21 commented on GitHub (Feb 21, 2020): All done, pull either `latest`, `2` or `2.1.1` docker image tag. Tested with arm64 and rpi3 w/ hypriot
Author
Owner

@talondnb commented on GitHub (Feb 21, 2020):

Working fine again, thank you!

<!-- gh-comment-id:589564285 --> @talondnb commented on GitHub (Feb 21, 2020): Working fine again, thank you!
Author
Owner

@robertolanuti commented on GitHub (Jul 18, 2020):

Hi,

I'm geting a smilar error with rpi4 64 bit (using the official OS 32 bit).

uname -a
Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

This are the images that I'm using:
app:
image: jc21/nginx-proxy-manager:latest

db:
image: jc21/mariadb-aria:latest

<!-- gh-comment-id:660484900 --> @robertolanuti commented on GitHub (Jul 18, 2020): Hi, I'm geting a smilar error with rpi4 64 bit (using the official OS 32 bit). uname -a Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux This are the images that I'm using: app: image: jc21/nginx-proxy-manager:latest db: image: jc21/mariadb-aria:latest
Author
Owner

@robertolanuti commented on GitHub (Jul 18, 2020):

Update: I'm able to run succesfully it by using the following db image:
db:
image: yobasystems/alpine-mariadb:latest

<!-- gh-comment-id:660494968 --> @robertolanuti commented on GitHub (Jul 18, 2020): Update: I'm able to run succesfully it by using the following db image: db: image: yobasystems/alpine-mariadb:latest
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#262
No description provided.