Open rg9400 opened 1 month ago
Having the same problem
PiHole worked for months. No docker compose or pihole config changes were done. Only a Docker Desktop Upgrade to 4.35.0 (172550)
Hi @rg9400, thanks for reporting. This should be fixed in the next release.
Just tested 4.35.1
Not fixed in this patch version. Maybe in the next minor version 4.36.0?
https://docs.docker.com/desktop/release-notes/#4351
@baumheld Sorry for the confusion, I wasn't expecting a patch release to be made. 4.35.1 fixes a single, critical issue. The fix for 53/udp will be released in 4.36, which is due some time soon.
Absolute newbie here following a tutorial and also was getting this error. Even though I just downloaded Docker Desktop fresh, it was 4.35.1 I believe. In app it said no updates available, but I saw 4.36 listed in release notes. I hit check for updates. It offered 4.36 and now I entered that command and not getting a port53 error.
Description
Starting from Docker version 4.35.0, I cannot bind port 53/udp into a container even though nothing is listening on it, breaking adguard/pihole. Downgrading to 4.34.3 instantly fixes the issue. Reproduced on a completely fresh install. I get the below error
Error response from daemon: Ports are not available: exposing port UDP 0.0.0.0:53 -> 0.0.0.0:0: listen udp4 0.0.0.0:53: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
Reproduce
Expected behavior
Docker should let me bind to this port because it's required for any container required to act as DNS. If I remove the /udp part, the container gets created but DNS queries do not seem to be properly filtering through that container like when udp was allowed on the earlier version
docker version
docker info
Diagnostics ID
33E30AF5-4884-4E19-A2A6-CE186A66A788/20241026212349
Additional Info
No response