-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
javax.net.ssl.SSLException: hostname in certificate didn't match: <gcr.io/64.233.166.82> != <*.googlecode.com> OR ... #1390
Comments
Hi @nirdothan, For the project using Spring Boot 1.4, let's force using particular versions of Google HTTP Client and Apache HttpClient for building. (BTW, your buildscript {
repositories {
mavenCentral()
...
}
dependencies {
...
classpath('com.google.http-client:google-http-client:1.23.0') {
force = true
}
classpath('org.apache.httpcomponents:httpcore:4.0.1') {
force = true
}
classpath('org.apache.httpcomponents:httpclient:4.0.1') {
force = true
}
}
} |
If the above doesn't resolve the issue, is it possible to get us a very small sample (hello-world like would be good) that reproduces this issue? |
Hi @chanseokoh, |
Thanks for the update. It helps us and other users going forward. I guess your project dependencies pulled in either Google HTTP Client or Apache HttpClient version that was not able to handle this kind of cert for some reason. Perhaps an old version. It'd be interesting to see which library versions the build was using by checking the Gradle dependency report. It might also be the case it is enough to force I'll close the issue. Feel free to update if you have any suggestions. |
following additional experimentation I realized that I already had here's the latest working configuration (just the buildscript part):
|
Huh, interesting. Thanks for the update. |
Description of the issue:
Build image failed when running with Gradle in an oldish Spring Boot 1.4 project. New Spring Boot 2.0 projects built in the same computer run fine. Suspecting that some of the unrelated project dependencies are causing the issue. Note that a similar issue happens if I change my jib.from config to pull from dockerhub, then I get a message that dockerhub certs don't match.
Expected behavior: project should build and publish
Steps to reproduce: ./gradlew jib
Environment: OSX 0.14.2, java version "1.8.0_191", Gradle 4.6
jib-gradle-plugin
Configuration:Log output:
Additional Information:
can also send my gradle dependencies report if you suspect that it'll be useful
The text was updated successfully, but these errors were encountered: