Closed eriksjolund closed 1 month ago
The fix is already WIP in https://github.com/containers/netavark/pull/965 and https://github.com/containers/aardvark-dns/pull/447 so you can expect the fix in the next netavarkv/aardvark-dns version
Fixed in netavarkv/aardvark-dns 1.11
Issue Description
Docker recently changed how DNS requests are handled from internal networks. Adjust the Podman compatibility rest API to match the new behaviour of the Docker rest API.
Side note: Podman already has functionality for disabling DNS (see the
podman network create
command-line option --disable-dns).Steps to reproduce the issue
Steps to reproduce the issue
Create the file
/tmp/test.bash
with the file contentssudo -i
systemctl start podman.socket
bash /tmp/test.bash /run/podman/podman.sock test1
useradd test
usermod -aG docker test
systemctl start docker.socket
machinectl shell --uid test
systemctl --user start podman.socket
bash /tmp/test.bash $XDG_RUNTIME_DIR/podman/podman.sock test2
bash /tmp/test.bash /var/run/docker.sock test3
Describe the results you received
Step 4 prints the following output
Step 10 prints the following output:
Step 11 prints the following output:
Describe the results you expected
I would have expected seeing
in step 4 and step 10, in a similar way as it can be seen in step 11.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting