workaround

• step1 stop harbor containers

sudo docker compose down -v

• step2 edit the/common/config/nginx/nginx.conf file, if internal_tls is enabled please also edit/common/config/portal/nginx.conf as well

## remove this line 
listen [::]:8443 ssl; 

## save file

• step3 restart harbor

sudo docker compose up -d

to keep consistent of our upgrade path, e.g. from 2.9.3 (if with ip_family config) and migrate to 2.10.0(without ip_family_config), we will only add this new ip_family configuration since v2.11 and do following reverse:

• remove ip_family config jinja migrate template for both version_2_9 and version_2_10 on main release(remove ipfamily config migrate jinja in 2.9 and 2.10 #19949)
• reverse ip_family config, ipv6 port nginx stetting, remove jinja migrate template for both version_2_9 and version_2_10 on release-2.10.0 (reverse ip_family config for release-2.10 #19950)
• reverse ip_family config, ipv6 port nginx stetting, remove jinja migrate template for both version_2_9 on release-2.9.0 (reverse ip_family config for release-2.9 #19951)

With all these changes, in case of you review this issue/prs with confusion, you should be aware of

• users could use ip_family config only since v2.11+
• users would like to use listen [::]:8443 ssl config in nginx related components below v2.11 should add this manually.
• users use v2.9.2 and migrate to 2.10.x need to add this listen [::]:8443 ssl manually if ipv6 address port is necessary in your network stack.

All prs merged, close it