Same ports get assigned to running pods if IPv6 is enabled

[barnabasbusa]

What's your CLI version?

90.1

Description & steps to reproduce

Have ipv6 enabled on your network, computer and docker network.

Run an enclave with many port forwards.

77007b8e4f4a   ethpandaops/dora:latest                             "./dora-explorer -co…"   About a minute ago   Up About a minute   0.0.0.0:32837->8080/tcp, :::32835->8080/tcp                                                                                                                                                                                                                                        dora--9ffa4a6eedd74092adcce2d9e8829191

d3da649b7d99   ethpandaops/lighthouse:stable                       "lighthouse beacon_n…"   About a minute ago   Up About a minute   0.0.0.0:32836->4000/tcp, :::32834->4000/tcp, 0.0.0.0:32835->5054/tcp, :::32833->5054/tcp, 0.0.0.0:32777->9000/udp, 0.0.0.0:32834->9000/tcp, :::32777->9000/udp, :::32832->9000/tcp                                                                                                 cl-1-lighthouse-geth--86bf547babf14378b962855a77328d89

Dora port forwards :::32835->8080/tcp - IPv6
Lighthouse port forwards: 0.0.0.0:32835->5054/tcp - IPv4

There should be no port clashes even if the IP stack is different, as this can cause confusions.

Desired behavior

Have unique ports forwarded on both IP stacks.

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

CLI: the Command Line Interface