openshift
feature: add opencontainers label to the quay.io/openshift/origin-console docker image
I would like the distributed docker image to contain org.opencontainers.image.source label for easy reference back to this repository. This is useful for tools like Renovate that makes updates to repositories when this image gets updates. OCI has standardized a few labels for adding metadata to images: https://github.com/opencontainers/image-spec/blob/main/annotations.md
Currently this is the list of labels:
$ docker inspect quay.io/openshift/origin-console:4.16.0 --format '{{ json .Config.Labels }}' | jq
{
"License": "Apache 2.0",
"architecture": "x86_64",
"build-date": "2024-03-07T02:59:05",
"com.redhat.build-host": "cpt-1001.osbs.prod.upshift.rdu2.redhat.com",
"com.redhat.component": "openshift-enterprise-console-container",
"com.redhat.license_terms": "https://www.redhat.com/agreements",
"description": "This is the base image from which all OpenShift Container Platform images inherit.",
"distribution-scope": "public",
"io.buildah.version": "1.32.2",
"io.k8s.description": "This is a component of OpenShift Container Platform and provides a web console.",
"io.k8s.display-name": "OpenShift Console",
"io.openshift.build.commit.author": "",
"io.openshift.build.commit.date": "",
"io.openshift.build.commit.id": "8c91a27550bb551aaee796d72fb8cd748af412f1",
"io.openshift.build.commit.message": "",
"io.openshift.build.commit.ref": "master",
"io.openshift.build.commit.url": "https://github.com/openshift/images/commit/2266a7f12fa725b3cd915b6195c9a8d297d01162",
"io.openshift.build.name": "",
"io.openshift.build.namespace": "",
"io.openshift.build.source-context-dir": "",
"io.openshift.build.source-location": "https://github.com/openshift/console",
"io.openshift.expose-services": "",
"io.openshift.maintainer.component": "Release",
"io.openshift.maintainer.project": "OCPBUGS",
"io.openshift.tags": "openshift,console",
"maintainer": "Samuel Padgett <[email protected]>",
"name": "openshift3/ose-console",
"release": "202403070215.p0.g2266a7f.assembly.stream.el8",
"summary": "Provides the latest release of the Red Hat Extended Life Base Image.",
"url": "https://access.redhat.com/containers/#/registry.access.redhat.com/openshift/ose-base/images/v4.16.0-202403070215.p0.g2266a7f.assembly.stream.el8",
"vcs-ref": "8c91a27550bb551aaee796d72fb8cd748af412f1",
"vcs-type": "git",
"vcs-url": "https://github.com/openshift/console",
"vendor": "Red Hat",
"version": "v4.16.0"
}
So you already got a few labels with metadata, but it would be nice if the standardized OCI labels was used in addition.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale