Skip to content
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

Closed
langdon opened this issue Nov 13, 2019 · 12 comments
Closed

configuration option for dns server to use #4508

langdon opened this issue Nov 13, 2019 · 12 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@langdon
Copy link

langdon commented Nov 13, 2019

/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:

Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64

Package info (e.g. output of rpm -q podman or apt list podman):

podman-1.6.2-2.fc31.x86_64
@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 13, 2019
@mheon
Copy link
Member

mheon commented Nov 13, 2019

@rhatdan @QiWang19 Looks like a good candidate for containers.conf

@larsks
Copy link
Contributor

larsks commented Nov 14, 2019

Note that this is already possible in Docker, which lets you set the default resolver via /etc/docker/daemon.json (or as a command line argument to dockerd). I've hit the same problem as langdon and I agree that always having to add --dns a.b.c.d to my podman run invocations is annoying (particularly when I forget!).

@baude
Copy link
Member

baude commented Nov 17, 2019

@rhatdan containers.conf ?

@rhatdan
Copy link
Member

rhatdan commented Nov 18, 2019

Yes @QiWang19 could easily add this option.

@rhatdan
Copy link
Member

rhatdan commented Dec 16, 2019

Begin adding support containers/common#29

@ensc
Copy link

ensc commented Jan 8, 2020

Is this available in 1.7.0? containers.conf seems to be ignored with podman-1.7.0-0.5.rc2.fc31.x86_64

@mheon
Copy link
Member

mheon commented Jan 8, 2020

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.

@larsks
Copy link
Contributor

larsks commented Jan 13, 2020

@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.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Feb 13, 2020

@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.

@rhatdan
Copy link
Member

rhatdan commented Jun 9, 2020

containers.conf support is now in.

@rhatdan rhatdan closed this as completed Jun 9, 2020
@langdon
Copy link
Author

langdon commented Jun 30, 2020

\o/

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

No branches or pull requests

8 participants