You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Docker server is TCP 2376 and enable TLS
when execute dive tomcat:9-jdk21-openjdk-slim-bullseye,get error with "could not read CA certificate "~/.docker/ca.pem": open ~/.docker/ca.pem: no such file or directory". But in actural,I have ca.pem and cert.pem and key.pem under ~/.dockerdirectory.
Because when execute docker ps or docker images ,I can get normal output
What you expected to happen:
dive can display image content
How to reproduce it (as minimally and precisely as possible):
1.reference https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket
2.execute dive tomcat:9-jdk21-openjdk-slim-bullseye`
Anything else we need to know?:
Environment:
OS version : Centos 9 stream
Docker version (if applicable) 27.1.1
[root@dockertest ~]# docker version
Client: Docker Engine - Community
Version: 27.1.1
API version: 1.46
Go version: go1.21.12
Git commit: 6312585
Built: Tue Jul 23 19:58:57 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.1.1
API version: 1.46 (minimum version 1.24)
Go version: go1.21.12
Git commit: cc13f95
Built: Tue Jul 23 19:57:11 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.19
GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc:
Version: 1.7.19
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
dive version : 0.12.0
[root@dockertest ~]# dive --version
dive 0.12.0
Cert file list
[root@dockertest .docker]# ls -l ~/.docker
total 64
-r--------. 1 root root 1526 Apr 29 08:41 ca-certs.crt
-rw-r--r--. 1 root root 1526 Apr 29 08:41 ca.pem
-rw-r--r--. 1 root root 745 Aug 8 22:02 cert.pem
-r--------. 1 root root 745 Aug 8 22:02 client.crt
-rw-r-----. 1 root root 351 Aug 8 22:02 client.csr
-r--------. 1 root root 241 Aug 8 22:02 client.key
-rw-------. 1 root root 2439 Aug 8 22:02 client.pfx
-rw-------. 1 root root 138 Aug 9 10:52 config.json
drwxr-x---. 3 root root 18 Aug 8 10:17 contexts
-rw-r-----. 1 root root 1686 Aug 8 22:02 docker.conf
-rw-r-----. 1 root root 1326 Aug 8 22:02 docker-readme.txt
-rw-r-----. 1 root root 75 Aug 8 22:02 ec_param.txt
-rw-r--r--. 1 root root 241 Aug 8 22:02 key.pem
-rw-r-----. 1 root root 802 Aug 8 22:02 server.crt
-rw-r-----. 1 root root 355 Aug 8 22:02 server.csr
-rw-------. 1 root root 241 Aug 8 22:02 server.key
-rw-------. 1 root root 2471 Aug 8 22:02 server.pfx
execute docker images and ourput
[root@dockertest .docker]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
tomcat 9-jdk21-openjdk-slim-bullseye 1df941cf8cb3 11 months ago 459MB
Image Source: docker://tomcat:9-jdk21-openjdk-slim-bullseye
Fetching image... (this can take a while for large images)
cannot fetch image
could not read CA certificate "~/.docker/ca.pem": open ~/.docker/ca.pem: no such file or directory
The text was updated successfully, but these errors were encountered:
What happened:
Docker server is TCP 2376 and enable TLS
when execute
dive tomcat:9-jdk21-openjdk-slim-bullseye
,get error with "could not read CA certificate "~/.docker/ca.pem": open ~/.docker/ca.pem: no such file or directory". But in actural,I haveca.pem and cert.pem and key.pem
under~/.docker
directory.Because when execute
docker ps
ordocker images
,I can get normal outputWhat you expected to happen:
dive can display image content
How to reproduce it (as minimally and precisely as possible):
1.reference
https://docs.docker.com/engine/security/protect-access/#use-tls-https-to-protect-the-docker-daemon-socket
2.execute dive tomcat:9-jdk21-openjdk-slim-bullseye`
Anything else we need to know?:
Environment:
Centos 9 stream
27.1.1
0.12.0
docker images
and ourput.bashrc
(part)docker info
dive tomcat:9-jdk21-openjdk-slim-bullseye
The text was updated successfully, but these errors were encountered: