[GH-ISSUE #683] Bug: Incompatible with Docker 29? #211

New issue

Closed

opened 2026-02-26 04:34:24 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 04:34:24 +03:00

Owner

Originally created by @freelock on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/683

What is Happening

I am using the Docker version of DNS Proxy Server, the latest published container, on a NixOS unstable host. With recent builds, DPS is failing to resolve.

I tracked this down to work with Docker 28, and fail with Docker 29.

What is Expected

When I log into a host with DPS running in Docker 28, I can ping host.docker and get the docker interface.

When I log into a host with the same exact config in Docker 29, I cannot ping host.docker, and get an error in the logs: dns-proxy-server m=solveAndSummarizeHandlingError status=solverFailed, currentSolverTime=0, totalTime=0, solver=SolverSystem, query=query=AAAA:host.docker, eClass=IllegalStateException, msg=Can't connect to docker API java.lang.IllegalStateException: Can't connect to docker API

... in both scenarios, /var/run/docker.sock is present inside the container, with the same permissions -- but in Docker 29 I get this error, and Docker 28 it works fine.

I'm not sure if there's any significant difference in NixOS's packaging between docker_28 and docker_29, but there are no other differences in my configuration other than changing this Docker version.

Specs

Docker Version: docker version

Working:

Client:
 Version:           28.5.2
 API version:       1.51
 Go version:        go1.25.5
 Git commit:        v28.5.2
 Built:             Thu Jan  1 00:00:00 1970
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          28.5.2
  API version:      1.51 (minimum version 1.24)
  Go version:       go1.25.5
  Git commit:       v28.5.2
  Built:            Tue Jan  1 00:00:00 1980
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.2.1
  GitCommit:        refs/tags/v2.2.1
 runc:
  Version:          1.3.3
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

Broken:

Client:
 Version:           29.1.3
 API version:       1.52
 Go version:        go1.25.5
 Git commit:        v29.1.3
 Built:             Thu Jan  1 00:00:00 1970
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          29.1.3
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.5
  Git commit:       v29.1.3
  Built:            Tue Jan  1 00:00:00 1980
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.2.1
  GitCommit:        refs/tags/v2.2.1
 runc:
  Version:          1.3.4
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

DPS Version:
- When running on standalone mode: ./dns-proxy-server --version
- When using docker: the docker image version or run the following if you are using the latest docker run --rm defreitas/dns-proxy-server --version

❯ docker run --rm  defreitas/dns-proxy-server --version
21:19:23.937 [main           ] DEB c.m.d.config.application.ConfigPathMapper         l=16   m=build                           status=configPathBuilt, path=/app/conf/config.json
21:19:24.061 [main           ] INF c.m.d.c.provider.jsonv1v2.dataprovider.JsonConfigsl=90   m=createDefaultConfigOnPath       status=createdDefaultConfigFile, path=/app/conf/config.json
21:19:24.064 [main           ] DEB c.m.d.c.p.jsonv1v2.dataprovider.ConfigDAOJson     l=28   m=find                            configPath=/app/conf/config.json
3.32.7-snapshot⏎

Attach DPS Log file

logs.txt

OS: [e.g. Ubuntu 16] - NixOS unstable

Originally created by @freelock on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/683 ## What is Happening I am using the Docker version of DNS Proxy Server, the latest published container, on a NixOS unstable host. With recent builds, DPS is failing to resolve. I tracked this down to work with Docker 28, and fail with Docker 29. ## What is Expected When I log into a host with DPS running in Docker 28, I can ping host.docker and get the docker interface. When I log into a host with the same exact config in Docker 29, I cannot ping host.docker, and get an error in the logs: dns-proxy-server m=solveAndSummarizeHandlingError status=solverFailed, currentSolverTime=0, totalTime=0, solver=SolverSystem, query=query=AAAA:host.docker, eClass=IllegalStateException, msg=Can't connect to docker API java.lang.IllegalStateException: Can't connect to docker API ... in both scenarios, /var/run/docker.sock is present inside the container, with the same permissions -- but in Docker 29 I get this error, and Docker 28 it works fine. I'm not sure if there's any significant difference in NixOS's packaging between docker_28 and docker_29, but there are no other differences in my configuration other than changing this Docker version. ## Specs * Docker Version: `docker version` Working: ``` Client: Version: 28.5.2 API version: 1.51 Go version: go1.25.5 Git commit: v28.5.2 Built: Thu Jan 1 00:00:00 1970 OS/Arch: linux/amd64 Context: default Server: Engine: Version: 28.5.2 API version: 1.51 (minimum version 1.24) Go version: go1.25.5 Git commit: v28.5.2 Built: Tue Jan 1 00:00:00 1980 OS/Arch: linux/amd64 Experimental: false containerd: Version: v2.2.1 GitCommit: refs/tags/v2.2.1 runc: Version: 1.3.3 GitCommit: docker-init: Version: 0.19.0 GitCommit: ``` Broken: ``` Client: Version: 29.1.3 API version: 1.52 Go version: go1.25.5 Git commit: v29.1.3 Built: Thu Jan 1 00:00:00 1970 OS/Arch: linux/amd64 Context: default Server: Engine: Version: 29.1.3 API version: 1.52 (minimum version 1.44) Go version: go1.25.5 Git commit: v29.1.3 Built: Tue Jan 1 00:00:00 1980 OS/Arch: linux/amd64 Experimental: false containerd: Version: v2.2.1 GitCommit: refs/tags/v2.2.1 runc: Version: 1.3.4 GitCommit: docker-init: Version: 0.19.0 GitCommit: ``` * DPS Version: * When running on standalone mode: `./dns-proxy-server --version` * When using docker: the docker image version or run the following if you are using the latest `docker run --rm defreitas/dns-proxy-server --version` ``` ❯ docker run --rm defreitas/dns-proxy-server --version 21:19:23.937 [main ] DEB c.m.d.config.application.ConfigPathMapper l=16 m=build status=configPathBuilt, path=/app/conf/config.json 21:19:24.061 [main ] INF c.m.d.c.provider.jsonv1v2.dataprovider.JsonConfigsl=90 m=createDefaultConfigOnPath status=createdDefaultConfigFile, path=/app/conf/config.json 21:19:24.064 [main ] DEB c.m.d.c.p.jsonv1v2.dataprovider.ConfigDAOJson l=28 m=find configPath=/app/conf/config.json 3.32.7-snapshot⏎ ``` * Attach DPS Log file [logs.txt](https://github.com/user-attachments/files/24614224/logs.txt) * OS: [e.g. Ubuntu 16] - NixOS unstable [1]: https://en.wikipedia.org/wiki/Minimal_reproducible_example

kerem

2026-02-26 04:34:24 +03:00

closed this issue
added the
duplicate
label

kerem commented

2026-02-26 04:34:25 +03:00

Author

Owner

@freelock commented on GitHub (Jan 13, 2026):

It looks like the Nixpkgs configuration is basically the same for the different Docker versions -- but I do see the "moby" package has some additional requirements/patchs applied when the version is at least 29 - it's adding a dependency on "nftables" and adding a -runc-v2 to a "containerd-shim" package name... https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/applications/virtualization/docker/default.nix

@freelock commented on GitHub (Jan 13, 2026): It looks like the Nixpkgs configuration is basically the same for the different Docker versions -- but I do see the "moby" package has some additional requirements/patchs applied when the version is at least 29 - it's adding a dependency on "nftables" and adding a -runc-v2 to a "containerd-shim" package name... https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/applications/virtualization/docker/default.nix

kerem commented

2026-02-26 04:34:25 +03:00

Author

Owner

@mageddo commented on GitHub (Jan 14, 2026):

Thanks for the report. I'll make the triage. Can you try the DPS latest snapshot to check if the error is the same?

@mageddo commented on GitHub (Jan 14, 2026): Thanks for the report. I'll make the triage. Can you try the DPS latest snapshot to check if the error is the same?

kerem commented

2026-02-26 04:34:25 +03:00

Author

Owner

@mageddo commented on GitHub (Jan 14, 2026):

Docker 29 is supported since DPS 4.0, see #637

@mageddo commented on GitHub (Jan 14, 2026): Docker 29 is supported since DPS 4.0, see #637