[GH-ISSUE #96] Brand new docker installation doesn't start #23

New issue

Open

opened 2026-02-27 14:47:29 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 14:47:29 +03:00

Owner

Originally created by @nodiaque on GitHub (Jun 22, 2025).
Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/96

Hello,

Trying to start a new install in docker and I only have crash.

[init] Setting up user nbxyz with PUID=99 and PGID=100
[init] Group with GID 100 already exists
[init] User with UID 99 already exists
_ _ _
_ __ | || | ___ ___ | |_ __ ___ _ ____
| '_ \ / _ \ | ' \ / _ \ / _ | | \ / / | | | /
| | | | / || |) | () | () | | _ > <| || |/ /
|| |_|_|_|./ _/ _/ _()/__, /|
|_/

If you enjoy netboot.xyz projects, please support us at:

https://opencollective.com/netbootxyz
https://github.com/sponsors/netbootxyz

[start] Starting supervisord (programs will run as nbxyz)
2025-06-22 13:32:28,480 INFO Set uid to user 0 succeeded
2025-06-22 13:32:28,482 INFO supervisord started with pid 1
2025-06-22 13:32:29,484 INFO spawned: 'nginx' with pid 20
2025-06-22 13:32:29,485 INFO spawned: 'dnsmasq' with pid 21
2025-06-22 13:32:29,487 INFO spawned: 'webapp' with pid 22
[dnsmasq] Starting TFTP server on port 69
[dnsmasq] TFTP root: /config/menus
[dnsmasq] TFTP security: enabled
[dnsmasq] Logging: enabled (dhcp and queries)
dnsmasq[21]: started, version 2.91 DNS disabled
dnsmasq[21]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-DNSSEC loop-detect inotify dumpfile
dnsmasq-tftp[21]: TFTP root is /config/menus secure mode
2025-06-22 13:32:29,490 WARN exited: nginx (exit status 1; not expected)
2025-06-22 13:32:29,694 WARN exited: webapp (exit status 1; not expected)
2025-06-22 13:32:30,696 INFO spawned: 'nginx' with pid 29
2025-06-22 13:32:30,696 INFO success: dnsmasq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-06-22 13:32:30,697 INFO spawned: 'webapp' with pid 30
2025-06-22 13:32:30,701 WARN exited: nginx (exit status 1; not expected)
2025-06-22 13:32:30,909 WARN exited: webapp (exit status 1; not expected)
2025-06-22 13:32:32,912 INFO spawned: 'nginx' with pid 37
2025-06-22 13:32:32,913 INFO spawned: 'webapp' with pid 38
2025-06-22 13:32:32,917 WARN exited: nginx (exit status 1; not expected)
2025-06-22 13:32:33,105 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2025-06-22 13:32:33,112 WARN exited: webapp (exit status 1; not expected)
2025-06-22 13:32:36,116 INFO spawned: 'webapp' with pid 53
2025-06-22 13:32:36,328 WARN exited: webapp (exit status 1; not expected)
2025-06-22 13:32:37,328 INFO gave up: webapp entered FATAL state, too many start retries too quickly

Originally created by @nodiaque on GitHub (Jun 22, 2025). Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/96 Hello, Trying to start a new install in docker and I only have crash. > > [init] Setting up user nbxyz with PUID=99 and PGID=100 > [init] Group with GID 100 already exists > [init] User with UID 99 already exists > _ _ _ > _ __ ___| |_| |__ ___ ___ | |_ __ ___ _ ____ > | '_ \ / _ \ __| '_ \ / _ \ / _ \| __| \ \/ / | | |_ / > | | | | __/ |_| |_) | (_) | (_) | |_ _ > <| |_| |/ / > |_| |_|\___|\__|_.__/ \___/ \___/ \__(_)_/\_\__, /___| > |___/ > > If you enjoy netboot.xyz projects, please support us at: > > https://opencollective.com/netbootxyz > https://github.com/sponsors/netbootxyz > > [start] Starting supervisord (programs will run as nbxyz) > 2025-06-22 13:32:28,480 INFO Set uid to user 0 succeeded > 2025-06-22 13:32:28,482 INFO supervisord started with pid 1 > 2025-06-22 13:32:29,484 INFO spawned: 'nginx' with pid 20 > 2025-06-22 13:32:29,485 INFO spawned: 'dnsmasq' with pid 21 > 2025-06-22 13:32:29,487 INFO spawned: 'webapp' with pid 22 > [dnsmasq] Starting TFTP server on port 69 > [dnsmasq] TFTP root: /config/menus > [dnsmasq] TFTP security: enabled > [dnsmasq] Logging: enabled (dhcp and queries) > dnsmasq[21]: started, version 2.91 DNS disabled > dnsmasq[21]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset no-nftset auth no-DNSSEC loop-detect inotify dumpfile > dnsmasq-tftp[21]: TFTP root is /config/menus secure mode > 2025-06-22 13:32:29,490 WARN exited: nginx (exit status 1; not expected) > 2025-06-22 13:32:29,694 WARN exited: webapp (exit status 1; not expected) > 2025-06-22 13:32:30,696 INFO spawned: 'nginx' with pid 29 > 2025-06-22 13:32:30,696 INFO success: dnsmasq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) > 2025-06-22 13:32:30,697 INFO spawned: 'webapp' with pid 30 > 2025-06-22 13:32:30,701 WARN exited: nginx (exit status 1; not expected) > 2025-06-22 13:32:30,909 WARN exited: webapp (exit status 1; not expected) > 2025-06-22 13:32:32,912 INFO spawned: 'nginx' with pid 37 > 2025-06-22 13:32:32,913 INFO spawned: 'webapp' with pid 38 > 2025-06-22 13:32:32,917 WARN exited: nginx (exit status 1; not expected) > 2025-06-22 13:32:33,105 INFO gave up: nginx entered FATAL state, too many start retries too quickly > 2025-06-22 13:32:33,112 WARN exited: webapp (exit status 1; not expected) > 2025-06-22 13:32:36,116 INFO spawned: 'webapp' with pid 53 > 2025-06-22 13:32:36,328 WARN exited: webapp (exit status 1; not expected) > 2025-06-22 13:32:37,328 INFO gave up: webapp entered FATAL state, too many start retries too quickly >

kerem commented

2026-02-27 14:47:29 +03:00

Author

Owner

@nodiaque commented on GitHub (Jun 22, 2025):

Turns out the problem was with the fact that I try to run it with uid and gid that is not the default. Once I switched, it work. Probably a perm issue somewhere

@nodiaque commented on GitHub (Jun 22, 2025): Turns out the problem was with the fact that I try to run it with uid and gid that is not the default. Once I switched, it work. Probably a perm issue somewhere

kerem commented

2026-02-27 14:47:29 +03:00

Author

Owner

@nodiaque commented on GitHub (Jun 22, 2025):

I think it's a compatibility problem with PUID = 99 and PGID = 100. These are the user we use for unraid and it doesn'T work when I put them back even if they have full access (and are owner) of the files

@nodiaque commented on GitHub (Jun 22, 2025): I think it's a compatibility problem with PUID = 99 and PGID = 100. These are the user we use for unraid and it doesn'T work when I put them back even if they have full access (and are owner) of the files

kerem commented

2026-02-27 14:47:29 +03:00

Author

Owner

@Aractor commented on GitHub (Oct 24, 2025):

I think it's a compatibility problem with PUID = 99 and PGID = 100. These are the user we use for unraid and it doesn'T work when I put them back even if they have full access (and are owner) of the files

Came here for the same issue. Running the docker container with the standard Unraid "nobody" user/group causes the fatal state error mentioned above. Switch back to the default 1000/1000 and everything loads properly, except now the container's files are owned by my user instead the nobody user.

@Aractor commented on GitHub (Oct 24, 2025): > I think it's a compatibility problem with PUID = 99 and PGID = 100. These are the user we use for unraid and it doesn'T work when I put them back even if they have full access (and are owner) of the files Came here for the same issue. Running the docker container with the standard Unraid "nobody" user/group causes the fatal state error mentioned above. Switch back to the default 1000/1000 and everything loads properly, except now the container's files are owned by my user instead the nobody user.

kerem commented

2026-02-27 14:47:29 +03:00

Author

Owner

@fmcatalan commented on GitHub (Dec 1, 2025):

Wanted to confirm that after switching the configured PUID 99 and PGID 100 for 1000/1000 it started working in Unraid.

Had this running for so long (years?) last week needed to boot and it was failing so I came to realize that the container wasn't running properly and this was the cause.

@fmcatalan commented on GitHub (Dec 1, 2025): Wanted to confirm that after switching the configured PUID 99 and PGID 100 for 1000/1000 it started working in Unraid. Had this running for so long (years?) last week needed to boot and it was failing so I came to realize that the container wasn't running properly and this was the cause.