Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
podman cannot create a rootless container that attempts to publish ports from a IPv6 address.

Version-Release number of selected component (if applicable):
Rhel 8.4 Ootpa with podman 3.0.1-7.module+el8.4.0+11311+9da8acfb
slirp4netns-1.1.8-1.module+el8.4.0+11311+9da8acfb.x86_64

How reproducible:
Just use podman create to create a rootless container that attempts to publish ports from a IPv6 address, then try to start it.

Steps to Reproduce:

$podman create --name test -p [2610:130:108:81::a5a:533]:6667:6667 alpine:latest sleep 30

$podman start <container ID>

Actual results:

Error: unable to start container "xxxxx": rootlessport listen tcp: address 2610:130:108:81::a5a:533:6667: too many colons in address

Expected results:
container should start

Additional info:

Found these on upstream
https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/62
https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/75

Matt,

IPV6 isn't supported in Podman yet right?  I think we're still sitting on https://github.com/containers/podman/issues/6114 and perhaps others.

We are presently in a limited support state. We support creating networks using IPv6 subnets and creating containers in those networks that will receive IPv6 addresses and be capable of full v6 connectivity. We do not support static IPv6 addresses and port forwarding with v6 addresses yet (both are slated to be part of the network rewrite). This (rootless v6 port forwarding) is not slated to be part of the rewrite - the required fix is outside of Podman, in rootlesskit - but it should not be a large change.

Hello Matthew,

I understand that rootless v6 port forwarding is not slated to be part of the rewrite. User is requesting for this feature. Would it be possible to implement this in future releases. If yes, we will raise an RFE for this.

Yes, it is definitely possible.

We've been doing further testing on this in preparation for the Podman v4.0 release, and we've discovered that it is already working in Podman v3.4, as shipped in RHEL 8.5.0.2; as such I'm going to CURRENTRELEASE this.