Feature Description
Arcane should display IPv6 address information for containers and networks alongside the existing IPv4 information. This includes the global IPv6 address of containers in the container detail view, as well as the IPv6 subnet and gateway of networks in the network detail view.
Problem It Solves
When running Docker with IPv6 enabled (via ipv6: true, default-network-opts, or enable_ipv6 in Compose), containers receive both IPv4 and IPv6 addresses. Arcane currently only surfaces the IPv4 address, which makes it look like IPv6 is not working - even though it actually is. The information is currently only visible in the "Inspect" tab of the container even though a user will most likely expect it to show up in the "Networks" tab.
Proposed Solution
In the container detail view, show the GlobalIPv6Address (and ideally IPv6Gateway) from NetworkSettings.Networks[*] next to the existing IPv4 fields. If a container is attached to multiple networks, show the IPv6 address per network the same way IPv4 is shown today.
In the network detail view, show IPv6 entries from IPAM.Config (subnet, gateway) so users can see at a glance whether a network is dual-stack.
The data is already available in the Docker API response - it's just a matter of rendering fields that are currently ignored.
Alternatives Considered
I am able to see this information in the Inspect tab of the container, but it would be nice if it would show up in the Networks tab, too. There is currently no way from the UI to inspect the network to see the IPv6 subnet/gateway.
Additional Context
No response
Would you be willing to work on this feature?
Feature Description
Arcane should display IPv6 address information for containers and networks alongside the existing IPv4 information. This includes the global IPv6 address of containers in the container detail view, as well as the IPv6 subnet and gateway of networks in the network detail view.
Problem It Solves
When running Docker with IPv6 enabled (via
ipv6: true,default-network-opts, orenable_ipv6in Compose), containers receive both IPv4 and IPv6 addresses. Arcane currently only surfaces the IPv4 address, which makes it look like IPv6 is not working - even though it actually is. The information is currently only visible in the "Inspect" tab of the container even though a user will most likely expect it to show up in the "Networks" tab.Proposed Solution
In the container detail view, show the
GlobalIPv6Address(and ideallyIPv6Gateway) fromNetworkSettings.Networks[*]next to the existing IPv4 fields. If a container is attached to multiple networks, show the IPv6 address per network the same way IPv4 is shown today.In the network detail view, show IPv6 entries from
IPAM.Config(subnet, gateway) so users can see at a glance whether a network is dual-stack.The data is already available in the Docker API response - it's just a matter of rendering fields that are currently ignored.
Alternatives Considered
I am able to see this information in the
Inspecttab of the container, but it would be nice if it would show up in theNetworkstab, too. There is currently no way from the UI to inspect the network to see the IPv6 subnet/gateway.Additional Context
No response
Would you be willing to work on this feature?