move info from docker readme to the docs #1321
Open
+165
−125
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
rdwebdesign
requested changes
Nov 27, 2025
PromoFaux
force-pushed
the
dockerdocs
branch
from
4a4e705 to
ee3d163
Compare
✅ Deploy Preview for pihole-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
PromoFaux
force-pushed
the
dockerdocs
branch
from
ee3d163 to
1a43a6b
Compare
Member
😕 😒 |
PromoFaux
force-pushed
the
dockerdocs
branch
2 times, most recently
from
c5345f4 to
5436b48
Compare
Signed-off-by: Adam Warner <[email protected]>
PromoFaux
force-pushed
the
dockerdocs
branch
from
5436b48 to
751b9c2
Compare
…instead Signed-off-by: Adam Warner <[email protected]>
rdwebdesign
reviewed
Dec 14, 2025
Comment on lines
+57
to
+71
| ## Docker tags and versioning | ||
|
|
||
| - `CAP_NET_BIND_SERVICE`: Allows FTLDNS binding to TCP/UDP sockets below 1024 (specifically DNS service on port 53) | ||
| - `CAP_NET_RAW`: use raw and packet sockets (needed for handling DHCPv6 requests, and verifying that an IP is not in use before leasing it) | ||
| - `CAP_NET_ADMIN`: modify routing tables and other network-related operations (in particular inserting an entry in the neighbor table to answer DHCP requests using unicast packets) | ||
| - `CAP_SYS_NICE`: FTL sets itself as an important process to get some more processing time if the latter is running low | ||
| - `CAP_CHOWN`: we need to be able to change ownership of log files and databases in case FTL is started as a different user than `pihole` | ||
| - `CAP_SYS_TIME`: FTL needs to be able to set the system time to update it using the Network Time Protocol (NTP) in the background | ||
| The primary docker tags are explained in the following table. [Click here to see the full list of tags](https://hub.docker.com/r/pihole/pihole/tags). See [GitHub Release notes](https://github.com/pi-hole/docker-pi-hole/releases) to see the specific version of Pi-hole Core, Web, and FTL included in the release. | ||
|
|
||
| !!! info | ||
| This image automatically grants those capabilities, if available, to the FTLDNS process, even when run as non-root. | ||
| The Date-based (including incremented "Patch" versions) do not relate to any kind of semantic version number, rather a date is used to differentiate between the new version and the old version, nothing more. | ||
|
|
||
| By default, docker does not include the `NET_ADMIN` capability for non-privileged containers, and it is recommended to explicitly add it to the container using `--cap-add=NET_ADMIN`. | ||
| Release notes will always contain full details of changes in the container, including changes to core Pi-hole components. | ||
|
|
||
| However, if DHCP and IPv6 Router Advertisements are not in use, it should be safe to skip it. For the most paranoid, it should even be possible to explicitly drop the `NET_RAW` capability to prevent FTLDNS from automatically gaining it. | ||
| | tag | description | | ||
| | :--- | :--- | | ||
| | `latest` | Always the latest release | | ||
| | `2022.04.0` | Date-based release | | ||
| | `2022.04.1` | Second release in a given month | | ||
| | `*beta` | Early beta releases of upcoming versions - here be dragons | | ||
| | `nightly` | Built and pushed whenever there are changes on the `development` branch and additionally produced by the scheduled nightly job. These are the most experimental development images and may change frequently | |
Member
There was a problem hiding this comment.
Maybe this block should be on the docker repo README, or maybe on both places.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR aim to accomplish?:
Trying to tidy up the docker readme a bit because it is getting unwieldy...
pi-hole/docker-pi-hole#1958
By submitting this pull request, I confirm the following:
git rebase)