Docker from itself installs images in quite random moments

Docker Desktop
1

After problems with one of the last versions of Windows’ version of Docker I have reinstalled Docker (from the Docker site, and updated it twice, up to version 4.42.1) and during the configuration I’ve observed that Docker installs some images:

alpine/socat

docker/jcat

The first one appeared first. At first I thought it was due to the configuration options, but since it had never done that before, I deleted that image and set the same options again to see if that was the reason. This time the first one didn’t appear, but the second one did, and not right away.
After a cursory search of the Internet, I decided to delete this image as well. For a while, it did not appear (several minutes), until, after browsing a few options from the menu on the left, it appeared again (the second one).
I thought maybe he needed it to display some Extensions or Docker Hub folder so I deleted it again and looked at those options again, but it didn’t appear, so that didn’t confirm my suspicion. After some time it appeared again.

Now I’m wondering, despite all these inconsistencies (new behavior, self-installing images, different images appearing at different times), is this nevertheless normal Docker behavior, or do I have a hole in my system and someone is trying to install more holes in the system for me, this time in Docker?

2

Without extensions, it should not fetch any unwanted images. As soon as you install extensions, any helper image required by the extension is pulled in as dependency.

.

1 Like
3

Maybe the new MCP Toolkit Beta? Gordon AI says about it:

Based on the provided context and my knowledge base, there is no direct evidence that the image with ID 76719466e8b9 (tagged as docker/jcat) is a dependency of the MCP Toolkit. The MCP Toolkit documentation mentions trusted MCP server containers and tools but does not reference the docker/jcat image or its functionality.

Additionally:

  • The image is marked as dangling and not in use, which further suggests it is not actively part of the MCP Toolkit.
  • The entry point /jcat and other metadata do not align with the MCP Toolkit’s described components or functionality.

If you suspect it might be related, you may need to check the MCP Toolkit’s specific configuration or dependencies directly.

Sources:

This blog article mention alpine/socat but not about installing an image :smiley: and not docker/jcat
I’ve disbled MCP Toolkit and enabled it again, but alpine/socat did not appear again. I’ll try to reinstall Docker again, as long as I have no data inside. God, give me patience for such nonsense.