NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
21.99k stars 2.53k forks source link

NPMv3 unable to start service prepare #2685

Open roswitina opened 1 year ago

roswitina commented 1 year ago

I have started version 3 in a Docker container under Debian 11 (incl. all updates) and I get the following error message in Portainer for "NginxProxyManager":

s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
❯ Checking folder structure ...
s6-rc: warning: unable to start service prepare: command exited 127
MattsBos commented 1 year ago

Getting the same error here, trying v3 today, just some additional messages in between:

s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
❯ Configuring npmuser ...
id: 'npmuser': no such user
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
s6-rc: warning: unable to start service prepare: command exited 127
vonl1 commented 1 year ago

Same problem dude

[root@Server npm-3]# docker logs npm-3-app-1 
❯ Configuring npm user ...
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
s6-rc: warning: unable to start service prepare: command exited 127
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

the v3 docker image infor

image

cfandora commented 1 year ago

same here

/init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error /init: 37: exec: s6-overlay-suexec: Exec format error

4 hours ago

image

github-actions[bot] commented 7 months ago

Issue is now considered stale. If you want to keep it open, please comment :+1:

roberto-iannone-riatlas commented 5 months ago

uising the following docker compose:

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:v3'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencypt:/etc/letsencrypt

got the following:

Attaching to app-1
app-1  | ❯ Configuring npm user ...
app-1  | ❯ Configuring npm group ...
app-1  | ❯ Checking paths ...
app-1  | ❯ Setting ownership ...
app-1  | ❯ Dynamic resolvers ...
app-1  | s6-rc: warning: unable to start service prepare: command exited 127
app-1  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

it seems only a warning but the container stucks. Any news about this issue?