Closed freelock closed 3 weeks ago
User error, sorry! It's working fine.
The issue turned out to be that the Nix podman package needs a firewall rule to allow access to the DNS port, when using a custom network. After opening that, DPS is working fine.
What is Happening
Hi,
I have DPS working in Nix with Docker, but was wanting to switch over to Podman. I made a bunch of changes in my configuration to swap Docker for Podman, and have things loading up and working, except for DPS -- and this is making it so DNS lookups inside any container fail.
I am seeing a java.lang.NullPointerException thrown over and over again in the logs, every 7 - 20 seconds or so. I am using the dfrietas/dns-proxy-server:latest container image for this, with Podman set with active Docker emulations enabled for the Docker socket and command.
Here's the exception:
... I am getting a similar exception using Docker in Nix, but just once and then everything seems to work. With Podman, this exception, and it looks like another saying Broken pipe repeat over and over again, and DNS inside the containers is not resolving (it does appear to be working mostly on the host):
What is Expected
That DPS works when running Podman, at least with Docker compatibility set up.
Changes (Optional)
Steps to implement the desired feature.