x509 certificate invalid when docker compose up -d

[vincenthcui]

• I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

run docker compose up -d but can't pull image from https://seata.io

➜  seata-go-server git:(master) docker compose up -d
[+] Building 1.3s (13/13) FINISHED
 => [seata-proxy internal] load build definition from Dockerfile                                                                  0.0s
 => => transferring dockerfile: 65B                                                                                               0.0s
 => [seata1 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata2 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata-dashboard internal] load build definition from Dockerfile                                                              0.0s
 => => transferring dockerfile: 69B                                                                                               0.0s
 => [seata3 internal] load build definition from Dockerfile                                                                       0.0s
 => => transferring dockerfile: 66B                                                                                               0.0s
 => [seata-proxy internal] load .dockerignore                                                                                     0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata1 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata2 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata-dashboard internal] load .dockerignore                                                                                 0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => [seata3 internal] load .dockerignore                                                                                          0.0s
 => => transferring context: 2B                                                                                                   0.0s
 => CANCELED [seata-proxy internal] load metadata for seata.io/seata-go-proxy:latest                                              0.9s
 => CANCELED [seata2 internal] load metadata for seata.io/seata-go-server:latest                                                  0.9s
 => ERROR [seata-dashboard internal] load metadata for seata.io/seata-go-dashboard:latest                                         0.8s
------
 > [seata-dashboard internal] load metadata for seata.io/seata-go-dashboard:latest:
------
The new 'docker compose' command is currently experimental. To provide feedback or request new features please open issues at https://github.com/docker/compose-cli
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to do request: Head https://seata.io/v2/seata-go-dashboard/manifests/latest: x509: certificate is valid for *.coding-pages.com, coding-pages.com, not seata.io

Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

start compose as expected

Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. git clone repo
2. run docker compose up -d

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

• JDK version :
• OS :
• Others: