New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS not working with containers on a single network. #11229
Comments
Doing some poking around, and it looks like our RHEL is pushing 3.0.2-Dev which is an odd thing to push by default so I am looking into that. I have also noticed that the DNS plugin is not present.
Show that there is no DNS plugin. So I tried adding it into the conflist file: After doing so SO I am looking to see if this is something I can install manually.... Any advise welcomed! |
@icsy7867 try git clone https://github.com/containers/dnsname.git
cd dnsname
go build -a
cp dnsname /usr/libexec/cni |
Thank you! I'll try this. ======= I tried this... I received an error: Also, I tried to follow the directions here:
===== Looks like I just needed to change into: go build -a worked after that.. ========= New problem. Things seemed OK. I created a new podman network (Which seemed to add all the correct dnsname bits), and then I tried launch a podman container using the new network and was greated with:
It looks like I need a newer version of glibc. Looks like our RHEL Satellite is pushing out 2.28. |
yup you can update glibc as well. |
The dnsname plugin can be installed with |
yes you can install from dnf as well, but i think you'll still need to update glibc if that is not updated as a dependency. |
For debian users, check this out: https://packages.debian.org/sid/golang-github-containernetworking-plugin-dnsname |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
Create a podman network
podman network create --name external
Create two pods on the same network (Mine are nginx and a mysql container). Also install iputils-ping in them. Lets call them some-nginx and some-mysql
try to ping one another using their container names:
podman exec -it some-nginx bash
ping some-mysql or ping some-mysql.dns.podman
Describe the results you received:
Temporary failure in name resolution
Describe the results you expected:
Successful pings
Additional information you deem important (e.g. issue happens only occasionally):
I have also tried to add --hostname to the deployments. Same results.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
The text was updated successfully, but these errors were encountered: