Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
DNS using container name fails for rootless containers on user-defined rootless cni network WITHIN a pod. The same succeeds for similar rootless containers NOT WITHIN a pod.
Steps to reproduce the issue:
normaluser@containerhost $> podman rm -fa # fresh set of examples
normaluser@containerhost $> podman network create myCNI
normaluser@containerhost $> podman network inspect myCNI | grep -i subnet
` "subnet": "10.89.0.0/24"`
normaluser@containerhost $> podman pod create --name myPod
normaluser@containerhost $> podman run --name myNginx2 --network myCNI --pod myPod -d nginx:alpine
normaluser@containerhost $> podman run --name myNginx3 --network myCNI --pod myPod -d nginx:alpine
normaluser@containerhost $> podman inspect myNginx2 | grep -i ipaddress
` "IPAddress": "10.89.0.2",`
normaluser@containerhost $> podman inspect myNginx3 | grep -i ipaddress
` "IPAddress": "10.89.0.3",`
normaluser@containerhost $> podman exec myNginx2 ping myNginx3
ping: bad address 'myNginx3'
normaluser@containerhost $> podman exec myNginx3 ping myNginx2
ping: bad address 'myNginx2'
Describe the results you received:
DNS lookup based on container name fails within pod
Describe the results you expected:
DNS lookup works for containers within a pod the way it works for containers not within pod
Additional information you deem important (e.g. issue happens only occasionally):
happens consistently and reproducably
Output of podman version:
Version: 2.1.1
API Version: 2.0.0
Go Version: go1.14
Built: Wed Dec 31 16:00:00 1969
OS/Arch: linux/amd64
Output of podman info --debug:
host:
arch: amd64
buildahVersion: 1.16.1
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: 'conmon: /usr/libexec/podman/conmon'
path: /usr/libexec/podman/conmon
version: 'conmon version 2.0.20, commit: '
cpus: 4
distribution:
distribution: debian
version: "10"
eventLogger: journald
hostname: arachne
idMappings:
gidmap:
- container_id: 0
host_id: 2000
size: 1
- container_id: 1
host_id: 100001
size: 65536
uidmap:
- container_id: 0
host_id: 2000
size: 1
- container_id: 1
host_id: 100001
size: 65536
kernel: 4.19.0-10-amd64
linkmode: dynamic
memFree: 369057792
memTotal: 2091732992
ociRuntime:
name: runc
package: 'runc: /usr/sbin/runc'
path: /usr/sbin/runc
version: |-
runc version 1.0.0~rc6+dfsg1
commit: 1.0.0~rc6+dfsg1-3
spec: 1.0.1
os: linux
remoteSocket:
path: /run/user/2000/podman/podman.sock
rootless: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: 'slirp4netns: /usr/bin/slirp4netns'
version: |-
slirp4netns version 1.1.4
commit: unknown
libslirp: 4.3.1-git
SLIRP_CONFIG_VERSION_MAX: 3
swapFree: 746057728
swapTotal: 1073737728
uptime: 184h 14m 26.29s (Approximately 7.67 days)
registries:
search:
- docker.io
- quay.io
version:
APIVersion: 2.0.0
Built: 0
BuiltTime: Wed Dec 31 16:00:00 1969
GitCommit: ""
GoVersion: go1.14
OsArch: linux/amd64
Version: 2.1.1
Package info (e.g. output of rpm -q podman or apt list podman):
podman/unknown,now 2.1.1~2 amd64 [installed]
podman/unknown 2.1.1~2 arm64
podman/unknown 2.1.1~2 armhf
podman/unknown 2.1.1~2 ppc64el
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Container host is a VirtualBox VM running on Fedora 32
podman packages installed from OpenSuse repo
$> cat "/etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list"
## "Kubic" repo from "OpenSuse" for "podman" packages since they aren't in Debian 10 (buster) repos
deb https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/Debian_10/ /
$> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
DNS using container name fails for rootless containers on user-defined rootless cni network WITHIN a pod. The same succeeds for similar rootless containers NOT WITHIN a pod.
Steps to reproduce the issue:
Describe the results you received:
DNS lookup based on container name fails within pod
Describe the results you expected:
DNS lookup works for containers within a pod the way it works for containers not within pod
Additional information you deem important (e.g. issue happens only occasionally):
happens consistently and reproducably
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Container host is a VirtualBox VM running on Fedora 32
podman packages installed from OpenSuse repo
$> cat "/etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list"
$> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"