Jib-gradle-plugin (containerizes w/o docker daemon) suddenly failing with SSL error

Question

We've been using Jib to generate and push a docker image to Docker Hub. This was working fine on May 10th, but failed on May 13th and has continued to fail ever since. I've rerun the pipeline that succeeded on May 10th and it now fails, so it seems to not be an issue in our repo files. Something outside of us has changed, but what? Here are the key error messages: * I/O error for image [registry-1.docker.io//] * javax.net.ssl.SSLPeerUnverifiedException * Certificate for doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com] * com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException: com.google.cloud.tools.jib.api.InsecureRegistryException: Failed to verify the server at https://registry-1.docker.io/v2/library/adoptopenjdk/blobs/sha256:881ba5607eb193aba90ef59e54d965e2d9b9e169a71f06ea3f72ab8349fa5e78 because only secure connections are allowed. Thoughts?

Thomas Kolmans · Answer

You're not alone, we're having the exact same issue. We've been trying to find a solution but have yet to find one. Edit: We have found a solution

Digging a bit deeper we finally found the solution through the following github issue: https://github.com/GoogleContainerTools/jib/issues/3058

In other words the answer is adding this:

buildscript {
    repositories {
        mavenCentral()
}
    dependencies {
        classpath('org.apache.httpcomponents:httpcore:4.4.12') { force = true }
        classpath('org.apache.httpcomponents:httpclient:4.5.10') { force = true }
        classpath('com.google.http-client:google-http-client:1.34.0') { force = true }
        classpath('com.google.http-client:google-http-client-apache-v2:1.34.0') { force = true }
    }
}