cli
cli copied to clipboard
Image for a running container not visible in docker image ls -a
Description
$ docker inspect 9371b7fe62b8 | grep Image | head -n 1
"Image": "sha256:97dcb0478f1af61327f1445da0f8e79490393eef9ad044ab07b64352f445841b",
$ docker image ls -a | grep 97
Reproduce
I don't have a clear idea how this situation came about. I checked with containerd disabled and it doesn't make the image visible.
Expected behavior
docker image ls -a
should show all images
docker version
Client:
Cloud integration: v1.0.35+desktop.13
Version: 26.0.0
API version: 1.45
Go version: go1.21.8
Git commit: 2ae903e
Built: Wed Mar 20 15:14:46 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.29.0 (145265)
Engine:
Version: 26.0.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.8
Git commit: 8b79278
Built: Wed Mar 20 15:18:02 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client:
Version: 26.0.0
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.13.1-desktop.1
Path: /Users/betelgeuse/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.26.1-desktop.1
Path: /Users/betelgeuse/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container. (Docker Inc.)
Version: 0.0.27
Path: /Users/betelgeuse/.docker/cli-plugins/docker-debug
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/betelgeuse/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.23
Path: /Users/betelgeuse/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.4
Path: /Users/betelgeuse/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.1.0
Path: /Users/betelgeuse/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/betelgeuse/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.6.3
Path: /Users/betelgeuse/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/betelgeuse/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/betelgeuse/.docker/cli-plugins/docker-scan: no such file or directory
Server:
Containers: 6
Running: 5
Paused: 0
Stopped: 1
Images: 9
Server Version: 26.0.0
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc version: v1.1.12-0-g51d5e94
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.6.22-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 8
Total Memory: 7.755GiB
Name: docker-desktop
ID: a2bceada-b6cf-4ac8-86ea-a1667694c960
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 108
Goroutines: 149
System Time: 2024-04-14T17:55:47.999347719Z
EventsListeners: 19
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/betelgeuse/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Additional Info
docker info
output shows nine images. However, docker image ls
only has five.
Take what I suggest with a grain of salt, but it could be that the image object you're seeing when calling docker inspect
could be an intermediate image which is why it's not showing up in the docker image ls -a
call. (Docker image ls documentation)
Take what I suggest with a grain of salt, but it could be that the image object you're seeing when calling
docker inspect
could be an intermediate image which is why it's not showing up in thedocker image ls -a
call. (Docker image ls documentation)
Read the documentation and you will see that -a means showing also intermediate images.
-a, --all Show all images (default hides intermediate images)
Take what I suggest with a grain of salt, but it could be that the image object you're seeing when calling
docker inspect
could be an intermediate image which is why it's not showing up in thedocker image ls -a
call. (Docker image ls documentation)Read the documentation and you will see that -a means showing also intermediate images.
-a, --all Show all images (default hides intermediate images)
I saw that but misinterpreted what it meant. I thought -a, by default, hid intermediate images. My mistake