[GH-ISSUE #2705] 'cont-init: warning: some scripts exited nonzero' after update to v2.9.21 #1864

Closed
opened 2026-02-26 07:32:47 +03:00 by kerem · 1 comment
Owner

Originally created by @hugalafutro on GitHub (Mar 18, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2705

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

after recreating the stack with 2.9.21 I see some erorrs in log I didn't before, however everything seems to work fine as far as what I use (proxy hosts)

Nginx Proxy Manager Version

v2.9.21

To Reproduce
Steps to reproduce the behavior:

  1. destroy stack
  2. pull :latest
  3. docker compose up -d
  4. See error

Expected behavior

preferably no errors in log

Screenshots

n/a

Operating System

debian cloud vm

Additional context

nginx-proxy-manager_site19  | s6-rc: info: service s6rc-oneshot-runner: starting
nginx-proxy-manager_site19  | s6-rc: info: service s6rc-oneshot-runner successfully started
nginx-proxy-manager_site19  | s6-rc: info: service fix-attrs: starting
nginx-proxy-manager_site19  | s6-rc: info: service fix-attrs successfully started
nginx-proxy-manager_site19  | s6-rc: info: service legacy-cont-init: starting
nginx-proxy-manager_site19  | cont-init: info: running /etc/cont-init.d/01_perms.sh
nginx-proxy-manager_site19  | /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found
nginx-proxy-manager_site19  | cont-init: info: /etc/cont-init.d/01_perms.sh exited 127
nginx-proxy-manager_site19  | cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh
nginx-proxy-manager_site19  | /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied
nginx-proxy-manager_site19  | cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126
nginx-proxy-manager_site19  | cont-init: warning: some scripts exited nonzero
nginx-proxy-manager_site19  | s6-rc: info: service legacy-cont-init successfully started
nginx-proxy-manager_site19  | s6-rc: info: service prepare: starting
nginx-proxy-manager_site19  | ❯ Checking folder structure ...
nginx-proxy-manager_site19  | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/default.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/force-ssl.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/block-exploits.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/assets.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/proxy.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/ip_ranges.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/include/resolvers.conf
nginx-proxy-manager_site19  |   ❯ /etc/nginx/conf.d/production.conf
nginx-proxy-manager_site19  | ❯ Enabling IPV6 in hosts: /data/nginx
nginx-proxy-manager_site19  |   ❯ /data/nginx/default_host/site.conf
nginx-proxy-manager_site19  |   ❯ /data/nginx/proxy_host/1.conf
nginx-proxy-manager_site19  |   ❯ /data/nginx/proxy_host/3.conf
nginx-proxy-manager_site19  |   ❯ /data/nginx/dead_host/1.conf
nginx-proxy-manager_site19  |
nginx-proxy-manager_site19  | -------------------------------------
nginx-proxy-manager_site19  |  _   _ ____  __  __
nginx-proxy-manager_site19  | | \ | |  _ \|  \/  |
nginx-proxy-manager_site19  | |  \| | |_) | |\/| |
nginx-proxy-manager_site19  | | |\  |  __/| |  | |
nginx-proxy-manager_site19  | |_| \_|_|   |_|  |_|
nginx-proxy-manager_site19  | -------------------------------------
nginx-proxy-manager_site19  |
nginx-proxy-manager_site19  | s6-rc: info: service prepare successfully started
nginx-proxy-manager_site19  | s6-rc: info: service nginx: starting
nginx-proxy-manager_site19  | s6-rc: info: service frontend: starting
nginx-proxy-manager_site19  | s6-rc: info: service backend: starting
nginx-proxy-manager_site19  | s6-rc: info: service frontend successfully started
nginx-proxy-manager_site19  | s6-rc: info: service backend successfully started
nginx-proxy-manager_site19  | ❯ Starting nginx ...
nginx-proxy-manager_site19  | s6-rc: info: service nginx successfully started
nginx-proxy-manager_site19  | ❯ Starting backend ...
nginx-proxy-manager_site19  | s6-rc: info: service legacy-services: starting
nginx-proxy-manager_site19  | s6-rc: info: service legacy-services successfully started
nginx-proxy-manager_site19  | [3/18/2023] [6:27:21 AM] [Global   ] › ℹ  info      Generating SQLite knex configuration
nginx-proxy-manager_site19  | [3/18/2023] [6:27:21 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
nginx-proxy-manager_site19  | [3/18/2023] [6:27:23 AM] [Migrate  ] › ℹ  info      Current database version: none
nginx-proxy-manager_site19  | [3/18/2023] [6:27:23 AM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [Setup    ] › ℹ  info      Logrotate completed.
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
nginx-proxy-manager_site19  | [3/18/2023] [6:27:27 AM] [Global   ] › ℹ  info      Backend PID 105 listening on port 3000 ...
nginx-proxy-manager_site19  | [3/18/2023] [6:27:28 AM] [Nginx    ] › ℹ  info      Reloading Nginx
nginx-proxy-manager_site19  | [3/18/2023] [6:27:28 AM] [SSL      ] › ℹ  info      Renew Complete

Originally created by @hugalafutro on GitHub (Mar 18, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2705 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> after recreating the stack with 2.9.21 I see some erorrs in log I didn't before, however everything seems to work fine as far as what I use (proxy hosts) **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> v2.9.21 **To Reproduce** Steps to reproduce the behavior: 1. destroy stack 2. pull :latest 3. docker compose up -d 4. See error **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> preferably no errors in log **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> n/a **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> debian cloud vm **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> ``` nginx-proxy-manager_site19 | s6-rc: info: service s6rc-oneshot-runner: starting nginx-proxy-manager_site19 | s6-rc: info: service s6rc-oneshot-runner successfully started nginx-proxy-manager_site19 | s6-rc: info: service fix-attrs: starting nginx-proxy-manager_site19 | s6-rc: info: service fix-attrs successfully started nginx-proxy-manager_site19 | s6-rc: info: service legacy-cont-init: starting nginx-proxy-manager_site19 | cont-init: info: running /etc/cont-init.d/01_perms.sh nginx-proxy-manager_site19 | /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_perms.sh: not found nginx-proxy-manager_site19 | cont-init: info: /etc/cont-init.d/01_perms.sh exited 127 nginx-proxy-manager_site19 | cont-init: info: running /etc/cont-init.d/01_s6-secret-init.sh nginx-proxy-manager_site19 | /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: 20: /package/admin/s6-overlay-3.1.4.1/etc/s6-rc/scripts/cont-init: /etc/cont-init.d/01_s6-secret-init.sh: Permission denied nginx-proxy-manager_site19 | cont-init: info: /etc/cont-init.d/01_s6-secret-init.sh exited 126 nginx-proxy-manager_site19 | cont-init: warning: some scripts exited nonzero nginx-proxy-manager_site19 | s6-rc: info: service legacy-cont-init successfully started nginx-proxy-manager_site19 | s6-rc: info: service prepare: starting nginx-proxy-manager_site19 | ❯ Checking folder structure ... nginx-proxy-manager_site19 | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/default.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/force-ssl.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/block-exploits.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/assets.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/proxy.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/ip_ranges.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/include/resolvers.conf nginx-proxy-manager_site19 | ❯ /etc/nginx/conf.d/production.conf nginx-proxy-manager_site19 | ❯ Enabling IPV6 in hosts: /data/nginx nginx-proxy-manager_site19 | ❯ /data/nginx/default_host/site.conf nginx-proxy-manager_site19 | ❯ /data/nginx/proxy_host/1.conf nginx-proxy-manager_site19 | ❯ /data/nginx/proxy_host/3.conf nginx-proxy-manager_site19 | ❯ /data/nginx/dead_host/1.conf nginx-proxy-manager_site19 | nginx-proxy-manager_site19 | ------------------------------------- nginx-proxy-manager_site19 | _ _ ____ __ __ nginx-proxy-manager_site19 | | \ | | _ \| \/ | nginx-proxy-manager_site19 | | \| | |_) | |\/| | nginx-proxy-manager_site19 | | |\ | __/| | | | nginx-proxy-manager_site19 | |_| \_|_| |_| |_| nginx-proxy-manager_site19 | ------------------------------------- nginx-proxy-manager_site19 | nginx-proxy-manager_site19 | s6-rc: info: service prepare successfully started nginx-proxy-manager_site19 | s6-rc: info: service nginx: starting nginx-proxy-manager_site19 | s6-rc: info: service frontend: starting nginx-proxy-manager_site19 | s6-rc: info: service backend: starting nginx-proxy-manager_site19 | s6-rc: info: service frontend successfully started nginx-proxy-manager_site19 | s6-rc: info: service backend successfully started nginx-proxy-manager_site19 | ❯ Starting nginx ... nginx-proxy-manager_site19 | s6-rc: info: service nginx successfully started nginx-proxy-manager_site19 | ❯ Starting backend ... nginx-proxy-manager_site19 | s6-rc: info: service legacy-services: starting nginx-proxy-manager_site19 | s6-rc: info: service legacy-services successfully started nginx-proxy-manager_site19 | [3/18/2023] [6:27:21 AM] [Global ] › ℹ info Generating SQLite knex configuration nginx-proxy-manager_site19 | [3/18/2023] [6:27:21 AM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json nginx-proxy-manager_site19 | [3/18/2023] [6:27:23 AM] [Migrate ] › ℹ info Current database version: none nginx-proxy-manager_site19 | [3/18/2023] [6:27:23 AM] [Setup ] › ℹ info Creating a new JWT key pair... nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [Setup ] › ℹ info Wrote JWT key pair to config file: /app/config/production.json nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [Setup ] › ℹ info Logrotate Timer initialized nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [Setup ] › ℹ info Logrotate completed. nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized nginx-proxy-manager_site19 | [3/18/2023] [6:27:27 AM] [Global ] › ℹ info Backend PID 105 listening on port 3000 ... nginx-proxy-manager_site19 | [3/18/2023] [6:27:28 AM] [Nginx ] › ℹ info Reloading Nginx nginx-proxy-manager_site19 | [3/18/2023] [6:27:28 AM] [SSL ] › ℹ info Renew Complete ```
kerem 2026-02-26 07:32:47 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@jc21 commented on GitHub (Mar 18, 2023):

Ah yeah these are some leftover scripts from s6-overlay v2 that, while still supported by s6-overlay v3, are no longer required. You can safely ignore these errors. I'll remove them in the next version.

<!-- gh-comment-id:1474760084 --> @jc21 commented on GitHub (Mar 18, 2023): Ah yeah these are some leftover scripts from s6-overlay v2 that, while still supported by s6-overlay v3, are no longer required. You can safely ignore these errors. I'll remove them in the next version.
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#1864
No description provided.