-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
As mentioned in #8585 (comment) the rootless-cni-infra image needs to be rebuild and pushed to quay.io.
As a consequence the --network-alias feature is not yet working for podman 3.0
I locally build podman 3.0, migrated my local system and removed all networks and containers. After that I tried to use the --network-alias feature but with no success
Steps to reproduce the issue:
podman rm -af
podman network create test
podman run -d --rm --name alpine1 --network test --network-alias a1 alpine tail -f /dev/null
podman run --rm --network test alpine nslookup a1
Describe the results you received:
Server: 10.88.2.1
Address: 10.88.2.1:53
** server can't find a1: NXDOMAIN
** server can't find a1: NXDOMAIN
Describe the results you expected:
I'd like to be able to resolve a1
to the IP of the alpine1
container
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version
:
Version: 3.0.0-dev
API Version: 3.0.0
Go Version: go1.15.6
Git Commit: c3b39842ce76e3e3bfc843abfebeeb603f04591d
Built: Wed Jan 27 08:26:58 2021
OS/Arch: linux/amd64
Output of podman info --debug
:
host:
arch: amd64
buildahVersion: 1.19.2
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: /usr/bin/conmon ist in conmon 1:2.0.25-1 enthalten
path: /usr/bin/conmon
version: 'conmon version 2.0.25, commit: 05ce716ac6d1cfeeb27b9280832abd2e9d1a085f'
cpus: 4
distribution:
distribution: arch
version: unknown
eventLogger: journald
hostname: carbon
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65535
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65535
kernel: 5.10.11-arch1-1
linkmode: dynamic
memFree: 3780677632
memTotal: 8213794816
ociRuntime:
name: crun
package: /usr/bin/crun ist in crun 0.17-1 enthalten
path: /usr/bin/crun
version: |-
crun version 0.17
commit: 0e9229ae34caaebcb86f1fde18de3acaf18c6d9a
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
os: linux
remoteSocket:
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
selinuxEnabled: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: /usr/bin/slirp4netns ist in slirp4netns 1.1.8-1 enthalten
version: |-
slirp4netns version 1.1.8
commit: d361001f495417b880f20329121e3aa431a8f90f
libslirp: 4.4.0
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.1
swapFree: 8589930496
swapTotal: 8589930496
uptime: 28m 37.88s
registries:
search:
- docker.io
- registry.fedoraproject.org
- quay.io
- registry.access.redhat.com
- registry.centos.org
store:
configFile: /home/tino/.config/containers/storage.conf
containerStore:
number: 2
paused: 0
running: 2
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: /usr/bin/fuse-overlayfs ist in fuse-overlayfs 1.4.0-1 enthalten
Version: |-
fusermount3 version: 3.10.1
fuse-overlayfs: version 1.4
FUSE library version 3.10.1
using FUSE kernel interface version 7.31
graphRoot: /home/tino/.local/share/containers/storage
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 116
runRoot: /run/user/1000/containers
volumePath: /home/tino/.local/share/containers/storage/volumes
version:
APIVersion: 3.0.0
Built: 1611732418
BuiltTime: Wed Jan 27 08:26:58 2021
GitCommit: c3b39842ce76e3e3bfc843abfebeeb603f04591d
GoVersion: go1.15.6
OsArch: linux/amd64
Version: 3.0.0-dev
Package info (e.g. output of rpm -q podman
or apt list podman
):
na.
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.):