tls: failed to verify certificate: x509: certificate signed by unknown authority about login-action

[crazy-max]

Error response from daemon: Get "https://registry.***.io/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority

This means your Docker client does not trust the self-signed certificate of registry.akaiv.io. You need to put the certs on the host of the docker client (GitHub Runner). More info: https://docs.docker.com/engine/security/certificates/

[0n1dev]

@crazy-max

My certificate is a certificate signed by a CA. I have obtained a GoGetSSL Wildcard SSL certificate.

[t1]

@0n1dev : you may have a valid certificate, but it looks your local docker doesn't recognise the CA to be valid.

[SowMou]

I have the same problem

using docker/setup-buildx-action@v3 in my github actions workflow.
docker/login-action@v3 cannot connect to my private docker registry.

The error message is :
Logging into https://xx.yy.zz.tt:5003/repository/my-private-registry/...
Error response from daemon: Get "https://xx.yy.zz.tt:5003/v2/": tls: failed to verify certificate: x509: certificate signed by unknown authority.

will there be a way to inject our certificate into the docker root ca like java ?

      - name: Setup JDK 17
        id: java
        uses: actions/setup-java@v3
        with:
          java-version: 17
          distribution: temurin
          cache: maven
      - name: Execute a keytool import function
        run: sudo keytool --importcert -noprompt -trustcacerts -file nexus.crt -alias jetty  -keystore ${{ steps.java.outputs.path }}/lib/security/cacerts -storepass ${{ secrets.KEYSTORE_PASS }}