[SERVICES] INFO: Failed to start nscd
caused by custom UUID/GUID without perimissions to start services
#4743
Labels
π 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: