Image tag format is excessively verbose for local images

[rasmus-e]

Only images in remote repositories are shown in the IMAGES panel.

I have returned to 1.22.2.
Tests:

• Reset image "Config Explorer" to default settings (never changed anything);
• Rebooted, switched to 1.22.2, local images show;
• Tried 1.23.1 and 1.23.0 again, both have the issue of missing images;
• Returned to 1.22.2 again - now my images are visible.

(repeated the tests a couple times, result stands)

VsCode on Mac air (2020)

[bwateratmsft]

Can you share a screenshot of both 1.22.2 and 1.23.0?

[bwateratmsft]

Thanks @rasmus-e! It looks like the images are still there, under docker.io/file-storage and docker.io/javaworker. But it seems that we are including docker.io in image names when we didn't in 1.22.2.

[rasmus-e]

Ah, was just hiding the comment cos noticed the same.
I can work with that, no problem you may close the issue as warranted.

Thanks for quick responses, sorry for noise!

[bwateratmsft]

I think I'd like to change this, so I'll reopen the issue. The old behavior was essentially to not show docker.io or docker.io/library ahead of images which are implicitly in that namespace. This includes common base images (e.g. alpine, for which the most explicit full name would be docker.io/library/alpine), and locally-built images that aren't namespaced or tagged for a registry (e.g. mywebapp, which until it is explicitly namespaced or given a registry, Docker would assume it was meant for docker.io/library).

I'm going to include a very slight change to the old behavior, where an image with a namespace will still implicitly add the docker.io/. e.g. kindest/node:latest will show under docker.io/kindest/node. But, node:latest will just show under node.

[bwateratmsft]

A fix for this has been released in Docker extension version 1.23.2.