Naming issues around the Container registry and Tag Expiration Policies

Copying @trizzi research from another issue:

I found this stackoverflow helpful. Although I am still confused as to when we should use image vs. tag

  • Image: This is the filesystem layers and metadata used to package an application in a way to run containers. Each image must have an ID on a docker engine.
  • Registry: This is a server that holds images. Similar to how a Git server holds source code, or an artifact server for binaries, a registry is where you push and pull images to and from.
  • Repository: The path to a directory of images on a registry server is the repository. This includes the registry hostname and port if you aren't using the default Docker Hub registry. In an image reference, this repository is the part before the final colon and tag.
  • Tag: A specific image within a repository. If you do not specify a tag, docker will default to the tag name "latest". This is the part after the final colon, and is often used for a version number.

So, in the user interface we really only refer to the repository and tags. This is similar to how DockerHub does it in their UI.

Screen_Shot_2019-10-21_at_1.11.23_PM Screen_Shot_2019-10-21_at_1.11.34_PM

This means that how we have worded:

Screenshot_2019-10-15_at_17.09.14

It's misleading, while is true what we say the positioning of the message kinda implies that the above level is going to be garbage collected ( which is the repository ) and I think that is not true @ggelatti @sabrams to confirm.

Edited May 22, 2020 by Iain Camacho
Assignee Loading
Time tracking Loading