Sign-in fails on IPv6-only systems as Docker Desktop only attempt to use IPv4.

[ x] I have tried with the latest version of Docker Desktop
[ x] I have tried disabling enabled experimental features
[ ] I have uploaded Diagnostics
Diagnostics ID:

Expected behavior

Expect login/sign-in to function over IPv6 (it used to in earlier versions)

Actual behavior

After upgrading the Docker Desktop from an older release on an ipv6-only system, the sign-in now fails with... "Post "https://login.docker.com/oauth/token": dialing login.docker.com:443 with direct connection: connecting to 104.16.82.103:443: dial tcp 104.16.82.103:443: connect: network is unreachable"

Yes - this system is IPv6 only, the Docker Desktop should not even attempt to "dial" login.docker.com using IPv4, and even on a dual-stack system, it should try IPv6 first.

Information

Please, help us understand the problem. For instance:

Is it reproducible?

Yes

Is the problem new?

Relatively, I did not have the problem before I updated Docker Desktop, but I don't recall which version I had before I upgraded.

Did the problem appear with an update?

Yes

macOS Version:

12.6.3

Intel chip or Apple chip:

Intel

Docker Desktop Version:

4.17.0 (99724)

Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`

[2023-03-22T04:49:31.948952000Z][com.docker.diagnose][I] set path configuration to OnHost Starting diagnostics

[PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [FAIL] DD0038: is the connection to Docker working? HTTP GET https://login.docker.com: Get "https://login.docker.com": dialing login.docker.com:443 with direct connection: connecting to 104.16.83.103:443: dial tcp 104.16.83.103:443: connect: network is unreachable [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs?

Please investigate the following 1 issue:

1 : The test: is the connection to Docker working? Failed with: HTTP GET https://login.docker.com: Get "https://login.docker.com": dialing login.docker.com:443 with direct connection: connecting to 104.16.83.103:443: dial tcp 104.16.83.103:443: connect: network is unreachable

Some functions require access to Docker, possibly through a HTTP proxy.

Steps to reproduce the behavior

... make sure system has IPv6 connectivity and IPv6 DNS resolvers configured
... disable IPv4 in the TCP/IP settings,

docker / for-mac