Open betelgeuse opened 6 months ago
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
Description
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 imagesdocker version
docker info
Additional Info
docker info
output shows nine images. However,docker image ls
only has five.