-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
configuration option for dns server to use #4508
Comments
Note that this is already possible in Docker, which lets you set the default resolver via |
@rhatdan containers.conf ? |
Yes @QiWang19 could easily add this option. |
Begin adding support containers/common#29 |
Is this available in 1.7.0? |
I don't believe it is - we're expecting initial support to land in 1.8.0. We'll begin gradually deprecating libpod.conf at that time as well. |
@gbryant200 you seem to be in the wrong place: this is for bug reports about podman, which is an alternative to Docker. It's not for questions about Docker. |
A friendly reminder that this issue had no activity for 30 days. |
@whitel The latest containers.conf in github.com/containers/common, has support for the dns server issue. The PR to get containers.conf support into Podman is very close. One more issue to get it merged. |
containers.conf support is now in. |
\o/ |
/kind feature
also kind of a bug
Description
If you are using 127.0.0.1 in resolv.conf, podman appears to switch to using 8.8.8.8 in the containers it runs. In some networks that dns server may be blocked. You can work around this issue by passing
--dns=<my-dns-server>
but it would be nice to be able to set this system/user -wide.I propose an entry in to the libpod.conf file(s). However, a similar issue is fixed via resolv.conf (if I am reading it correctly) here: #3277
Docker/Moby had a similar problem: moby/moby#23910
Output of
podman version
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: