holysugar / docker-circleci-lighthouse

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Container ImageのOSのクライアント証明書が切れている

tayagi-aim opened this issue · comments

% docker run --name lighthouse -it holysugar/circleci-lighthouse /bin/bash                                                                          (git)-[master]
root@c012bdde961c:/lighthouse#
Display all 1068 possibilities? (y or n)
curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
root@c012bdde961c:/lighthouse# curl https://intoli.com/install-google-chrome.sh -v
* Hostname was NOT found in DNS cache
*   Trying 34.233.178.250...
* Connected to intoli.com (34.233.178.250) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS alert, Server hello (2):
* SSL certificate problem: certificate has expired
* Closing connection 0
* SSLv3, TLS alert, Client hello (1):
curl: (60) SSL certificate problem: certificate has expired
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
root@c012bdde961c:/lighthouse# curl https://intoli.com/install-google-chrome.sh -v^C
root@c012bdde961c:/lighthouse# uname -a
Linux c012bdde961c 5.15.49-linuxkit #1 SMP Tue Sep 13 07:51:46 UTC 2022 x86_64 GNU/Linux
root@c012bdde961c:/lighthouse# uname -r
5.15.49-linuxkit
root@c012bdde961c:/lighthouse# cat /etc/o
opt/        os-release
root@c012bdde961c:/lighthouse# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

当該コンテナimageに使っているOSのクライアント証明書がきれているためTLS overの通信ができていない(curl以外もだめそう)

コンテナimageのOSをアップグレードする。