You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In "Settings":
Enable NSCD (Name Service Cache Daemon) for caching all DNS requests: Enabled
In Logs:
[SETTINGS] INFO: Chrome executable is changed. Resetting Chrome...
[SERVICES] INFO: Starting nscd
[SERVICES] INFO: Failed to start nscd
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
[SETTINGS] INFO: Chrome executable is changed. Resetting Chrome...
[SERVICES] INFO: Starting nscd
[SERVICES] INFO: Failed to start nscd
π» 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
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
The text was updated successfully, but these errors were encountered: