Our great sponsors
-
That might be worth reporting it to the bug tracker. https://github.com/pi-hole/pi-hole/issues
-
https://github.com/pi-hole/docker-pi-hole/issues/610 The cause is, that the container needs specific user and group ids to be run at. If you are using persistent volumes these have to have the same uid and guid as the users running pihole. If that is not possible on the host, there is currently no way to fixing it. The dev team have to implement a environmental variable to set the uid and gid in the container itself. The workaround that works for me is to run it without a attached volume and just use the teleporter backup and restore when I’m rebuilding it.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.