Closed 0x022b closed 4 years ago
still with podman-1.7.0-0.5.rc2.fc31.x86_64
@haircommander @mheon PTAL
I think the safest option for this is to allow a local copy of /etc/resolv.conf, /etc/hosts for containers in a pod if they specify these options, instead of using the pod-level files.
To be clear, this means that --dns
will affect only one container in the pod, not the entire pod.
To change the entire pod, we'd want to add --dns
to podman pod create
.
To be clear, this means that
--dns
will affect only one container in the pod, not the entire pod.To change the entire pod, we'd want to add
--dns
topodman pod create
.
Sounds good to me. @rhatdan WDYT?
We are actually in the process of adding --dns
to podman pod create
.
:+1:
Hopefully @mheon patch #5241 gets in and we can close this issue.
/kind bug
Description
Unable to set DNS options for containers that are run in a pod.
Steps to reproduce the issue:
podman pod create --name dns-test
podman run -it --rm --pod dns-test --dns 1.1.1.1 --dns-search . alpine cat /etc/resolv.conf
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Physical machine