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
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
As mentioned in https://github.com/containers/podman/pull/8585#issuecomment-768409098 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:
Describe the results you expected:
I'd like to be able to resolve
a1
to the IP of thealpine1
containerAdditional 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
):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.):