Updates Docker Secrets usage information #1851
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Docker secrets has a couple of characteristics that may cause baffling errors where configuration looks correct but the pihole container cannot read the secret. The UID and GID of the secret file on the host must be set to the same value used by the pihole process in the container (typically 1000).
Description
Amends the WEBPASSWORD_FILE variable description to provide both Swarm and Compose related links. Directs reader to a docker secrets section in Tips and Tricks.
Adds Tips and Tricks content for docker secrets noting the requirement that the UID for the secrets file must be the same as the pihole process in the container. Otherwise the process will not be able to read the file.
Motivation and Context
Adds useful information that will reduce baffling problems reading a Docker secrets file (WEBPASSWORD_FILE).
How Has This Been Tested?
Tested on my two pihole instances (synology docker host).
Types of changes
Checklist: