it could be that the curl in the docker image for branch-1 is older and is missing some newer CAs.
Could we sidestep this issue by installing tooling from spotbugs instead? On Fri, Oct 8, 2021 at 10:54 PM 张铎(Duo Zhang) <[email protected]> wrote: > They all fail with docker image building failure. > > 10:50:04 Step 19/32 : RUN mkdir -p /opt/findbugs && curl -L -s -S > > > > > https://sourceforge.net/projects/findbugs/files/findbugs/3.0.1/findbugs-noUpdateChecks-3.0.1.tar.gz/download > > -o /opt/findbugs.tar.gz && tar xzf /opt/findbugs.tar.gz > > --strip-components 1 -C /opt/findbugs > > 10:50:05 ---> Running in d3ff60cd19b4 > > 10:50:05 [91mcurl: (60) SSL certific [0m [91mate problem: certificate > > has expired > > 10:50:05 More details here: http://curl.haxx.se/docs/sslcerts.html > > 10:50:05 > > 10:50:05 curl performs SSL certificate verification by default, using a > > "bundle" > > 10:50:05 of Certificate Authority (CA) public keys (CA certs). If the > > default > > 10:50:05 bundle file isn't adequate, you can specify [0m [91man > > alternate file > > 10:50:05 using the --cacert option. > > 10:50:05 If this HTTPS server uses a certificate signed by a CA > > represented in > > 10:50:05 the bundle, the certificate verification probably [0m [91m > > failed due to a > > 10:50:05 problem with the certificate (it might be expired, or the name > > might > > 10:50:05 not match the domain name in the U [0m [91mRL). > > 10:50:05 If you'd like to turn off curl's verification of the > > certificate, use > > 10:50:05 the -k (or --insecure) opt [0m [91mion. > > 10:50:06 [0mThe command '/bin/sh -c mkdir -p /opt/findbugs && curl > > -L -s -S > > > https://sourceforge.net/projects/findbugs/files/findbugs/3.0.1/findbugs-noUpdateChecks-3.0.1.tar.gz/download > > -o /opt/findbugs.tar.gz && tar xzf /opt/findbugs.tar.gz > > --strip-components 1 -C /opt/findbugs' returned a non-zero code: 60 > > 10:50:06 ERROR: Docker failed to build yetus/hbase:633d966bfe. > > > > But I tried the curl command locally and it could download the tarball > successfully. > > Not sure what the problem is, did anyone face this problem before? > > Thanks. >
