tart images pushed to gitlab container registry always show a publish date of right now

[cosmoshepcat]

Curious if anyone else has run into this but since these are not really docker images its probably not surprising.

if i do a tart push of a local vm to our remote container registry it works fine but in the gitlab ui it shows every image as always freshly pushed. refreshing over and over shows the image publish date updates with the time. i am assuming this is because some docker info is missing in a tart image that gitlab is looking for.

not a show stopper but this does make auto cleanup on various tart repos within gitlab impossible since it uses those publish dates.

[edigaryev]

This looks like a purely GitLab Registry's issue to me.

If you toggle the Use relative times setting in Preferences → Time preferences, you'll see that GitLab Registry simply leaves the timestamp uninitialized for manifests/configs that they fail to recognize and pull the timestamp from¹:

Compare this to GitHub:

¹: GitLab Registry pulls the created field from the manifest configuration object of type application/vnd.docker.container.image.v1+json. However, Tart uses a different media type of application/vnd.oci.image.config.v1+json. There exist a well-known annotation oci.opencontainers.image.created mentioned in the OCI Image Format Specification, but GitLab Registry doesn't seem to support it, judging from their source code.