New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SERVICES] INFO: Failed to start nscd #4743
Comments
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? |
Nscd is not configured to support changing the PUID/PGID to an unpriviliged user.
This subsystem not properly using the environment variable is a bug. (PRs welcome) Note The image currently only fully supports |
π 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: