NginxProxyManager / NginxProxyManager/nginx-proxy-manager

NPM fails to start : s6-rc fatal error

Open
#2,889 18 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Hi there, since the first timeI installed NPM it never started well. After a reboot of my server the container does start but there’s still this weird error :
s6-rc: info: service s6rc-oneshot-runner: starting 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 s6-rc: fatal: timed out s6-sudoc: fatal: unable to get exit status from server: Operation timed out /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.
I have to go to portainer and recreate the container at each of my server reboot so it starts well.
Here’s the steps to reproduce :
use this docker compose and just reboot your device where NPM is installed.
version: '3.8'services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- /home/louise/docker/NGINX/data:/data
- /home/louise/docker/NGINX/letsencrypt:/etc/letsencrypt
 

If anyone has any idea about how to fix s6-rc not working (I don’t even know what it is tbh), I take !

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied Docker Compose configuration and the container logs around the s6-rc prepare service after a host reboot. Reproduce the restart behavior and compare it with recreating the container; done means the container starts successfully after reboot without manual recreation and the timeout no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.