Could not see the images in Docker Desktop

Docker Desktop
1

I was able to see all the images in docker desktop under images. But all of a sudden from yesterday, I can see images with docker images command from CLI, but could not see them on docker desktop.

2

Same here. Docker Desktop does not show images, but docker cli displays it.

Mac OS Version Monterey
Verison 12.0.1 (21A559)

Docker
Client:
Cloud integration: v1.0.20
Version: 20.10.10
API version: 1.41
Go version: go1.16.9
Git commit: b485636
Built: Mon Oct 25 07:43:15 2021
OS/Arch: darwin/amd64
Context: default
Experimental: true

Server: Docker Engine - Community
Engine:
Version: 20.10.10
API version: 1.41 (minimum version 1.12)
Go version: go1.16.9
Git commit: e2f740d
Built: Mon Oct 25 07:41:30 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.11
GitCommit: 5b46e404f6b9f661a205e28d59c982d3634148f8
runc:
Version: 1.0.2
GitCommit: v1.0.2-0-g52b36a2
docker-init:
Version: 0.19.0
GitCommit: de40ad0

3

Sometimes you need to restart the Docker Desktop. It seems to be a bug. I have noticed it too.

1 Like
4

saved me a lot time this comment :slight_smile:

5

I still have this issue. Even after restart. OS: Windows 11

6

is no one helping with this problem? is not trivial and should be addressed ASAP. Iā€™m new in docker and iā€™m surprised no one helped solving this problem. i have the same. desktop see just the images i pulled not the ones i build myself.

7

If you think you found a bug, you can report it on GitHub

I could only recommend restarting Docker Desktop, which helped someone, but we had no more information to work with.. And the cause of an issue in 2025 could be totally different than it was in 2021. There were only a couple of reports about this o this forum for years, so it is probably hard to find the cause, but you can try the troubleshooting guide to collect logs and share it with the developers on GitHub as described here

Otherwise it depends on whether anyone in the community has an idea.

If you share more info here, that could also get more usersā€™ attention. For example exact Docker Desktop version, macOS version, The output of docker info and docker version after removing any private info from the output and share it in a code block surrounded by 3 backticks (not apostrophes) before and after the output like

```
output here
```

Docker Desktop also supports hiding system containers, so if there is any bug with handling that, you can try enabling all system containers. It can be found the extension settings or in the Kubernetes when it is enabled.

An incorrectly configured docker context or environment variable in the shell could also change what endpoint the docker client connects to from the terminal, but the same docker command should show all images built localy or pulled from a registry.

And you can try enabling or disabling the ā€œuse containerd for pulling and storing imagesā€ iin General settings, depending on whether you have it enbaled already or not. Letā€™s see if any of these help, and if not, I still recommend reporting it on GitHub..

8 
Client:
 Version:    28.1.1+1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.33.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 34
  Running: 4
  Paused: 0
  Stopped: 30
 Images: 6
 Server Version: 28.1.1+1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 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: 05044ec0a9a75232cad458027ca83437aae3f4da
 runc version: 
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.14.0-35-generic
 Operating System: Ubuntu Core 22
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 31.05GiB
 Name: alexander-bontempo-HP-ENVY
 ID: 12439f6f-6be0-4650-8cf0-152ede1bb5b4
 Docker Root Dir: /var/snap/docker/common/var-lib-docker
 Debug Mode: false
 Username: bontix77
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false

Client:
 Version:           28.1.1+1
 API version:       1.48
 Go version:        go1.23.8
 Git commit:        068a01e
 Built:             Fri Jun 13 16:11:30 2025
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          28.1.1+1
  API version:      1.49 (minimum version 1.24)
  Go version:       go1.23.8
  Git commit:       01f442b
  Built:            Fri Jun 13 16:12:14 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.27
  GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
  Version:          1.2.6
  GitCommit:        
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
9

Two observations:

  • You ignored that @rimelek asked you to share the output as code block, even though he shared an example on how to post a code block.
  • The output of docker info indicates that you are using the Snap package of Docker. The support channel for the Snap is the Ubuntu community. This forum is a support channel for Docker Desktop and Docker CE.

Please share the output of:

dpkg -l 'docker*' | grep '^ii'
snap list docker

When you share the outputs, always format your posts according to the following guide: How to format your forum posts

10

I formatted your output. As you see, without formatting, @meyay didnā€™t notice that you are using snap, not Docker Desktop (He did.I missed the second observation) . By the way this topic is in the ā€œDocker Desktopā€ category with the ā€œmacosā€ tag. That confused me first.

if you donā€™t use Docker Desktop or your client doesnā€™t connect to Docker Desktopā€™s Docker daemon, you wonā€™t see your built images in Docker Desktop.

You probably had the snap package automatically installed somehow (I heard about that before) and you are trying to use Docker Desktop on Linux.Here is the official documentation to install it:

You only need to install the docker client. Not the daemon on Linux.

You can also try to switch to the ā€œdesktop-linuxā€ context:

docker context use desktop-linux

Note: I am also sorry if I caused any confusion, because I had to edit my post many times.

11

i didnā€™t recall i installed docker with the app store. All fixed. i uninstalled everything and reinstalled properly the docker desktop+engine, all working smoothly now. thank you.

12

What do you mean by `docker destop+engine"? Please still share the output of the commands I asked for.

Note: Docker Desktop is not a frontend for a standalone or remote Docker Engine installation. Docker Desktop only interacts with its own Docker Engine that runs inside a utility vm controlled by Docker Desktop.

13

when you install docker desktop it install the engine too. But is all set for me.

14

Docker Desktop and the engine is two different product. The engine is also installed inside the virtual machine of Docker Desktop. The Snap package is also a separate project, not even supported by Docker Inc, so I am pretty sure it would not be installed by Docker Desktop, but it can be installed accidentally multiple ways. The engine on the same host is not needed for Docker Desktop and often causes problem when multiple variants of Docker are installed

Thatā€™s great. Thanks for the feedback.