Open RavHilton opened 1 month ago
I'm guessing setting the user ID is causing it to not have the correct permissions to start the service.
That is the UID/GID that Docker runs under, and 29 other containers run under without any issues. However when I comment these out Uptime Kuma can load nscd when it boots.
Hhmmm, does that mean I shouldn't set the PUID/PGID for Uptime Kuma even though it works fine for a heap of other containers, or is there something either a) needing changed in the official Uptime Kuma container, or b) I've missed in the docs/config?
does that mean I shouldn't set the PUID/PGID for Uptime Kuma
Nscd is not configured to support changing the PUID/PGID to an unpriviliged user.
needing changed in [...] Uptime Kuma
This subsystem not properly using the environment variable is a bug. (PRs welcome)
[!NOTE] The image currently only fully supports
root
-level-users (see #4500 for further details). Could be documented better as with most edge case configurations.
📑 I have found these related issues/pull requests
no response
🛡️ Security Policy
Description
In "Settings": Enable NSCD (Name Service Cache Daemon) for caching all DNS requests: Enabled
In Logs:
If I shell into the Docker container, I can manually start nscd with no issues.
👟 Reproduction steps
Current Docker container, using Compose, it does this all the time when "Enable NSCD" is set - disabling it in Settings obviously results in the container starting without this error message.
👀 Expected behavior
NSCD would start when enabled
😓 Actual Behavior
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
Docker
🌐 Browser
Opera, Chrome, Edge, Firefox
🖥️ Deployment Environment
Host: Synology DS1823xs+ Environment: Container Manager Management: Portainer CE 2.19.5
📝 Relevant log output