-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
--network-alias doesn't seem to work #8567
Comments
It will eventually work on rootless, but I don't believe the rootless CNI image has been rebuilt with a new-enough version of DNSName yet. |
Ah - I think you're entirely correct. We may want to add an error message if these are used by rootless until fixes can be made. |
A friendly reminder that this issue had no activity for 30 days. |
This requires the updates roootless CNI infra image. On hold until we can rework to build that image from the root FS, or someone decides to update the image we are actually using. |
I have opened a PR for the imageless rootless-cni-infra container #8910. The fix for this issue is also included in that PR. |
Make sure we pass the network aliases as capability args to the cnitool in the rootless-cni-infra container. Also update the dnsname plugin in the cni-infra container. Fixes containers#8567 Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
Make sure we pass the network aliases as capability args to the cnitool in the rootless-cni-infra container. Also update the dnsname plugin in the cni-infra container. Fixes containers#8567 Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When I try to use the new (since 2.2.0) network alias feature, it doesn't seem to work.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
I would like to be able to resolve
a1
to the IP of the first container.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
):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.):
Local laptop. The rootless-cni-infra image is
quay.io/libpod/rootless-cni-infra@sha256:304742d5d221211df4ec672807a5842ff11e3729c50bc424ea0cea858f69d7b7
The text was updated successfully, but these errors were encountered: