Skip to content

feat(docker): add OCI image provenance labels#455

Open
T012m3n7oR wants to merge 1 commit intorishikanthc:mainfrom
T012m3n7oR:feature/oci-image-labels
Open

feat(docker): add OCI image provenance labels#455
T012m3n7oR wants to merge 1 commit intorishikanthc:mainfrom
T012m3n7oR:feature/oci-image-labels

Conversation

@T012m3n7oR
Copy link
Copy Markdown

Summary

Adds OpenContainers image
annotations

on the final stage of the CPU, CUDA 12.6, and CUDA 12.9 Dockerfiles so
released images can be tied to git revision, version, build time, and
documentation.

Changes

  • Dockerfile — OCI LABEL block with build-args (VCS_REF,
    BUILD_DATE, VERSION, OCI_*).
  • Dockerfile.cuda / Dockerfile.cuda.12.9 — same pattern on the
    CUDA runtime stages; descriptions note the CUDA variant.

Defaults assume this repo’s canonical GitHub URLs on main. Optional
OCI_SOURCE, OCI_URL, and OCI_DOCUMENTATION remain available when an
image must advertise different canonical URLs.

CI / releases

Official pipelines should pass VCS_REF (full SHA), BUILD_DATE (RFC 3339
UTC), and VERSION (tag or git describe) so labels reflect the real
build.

Adds #452

Add OpenContainers image annotations on the final runtime stage for the
CPU, CUDA 12.6, and CUDA 12.9 Dockerfiles. Images expose the standard
label set (title, description, revision, version, created, source, url,
documentation, licenses).

Default ARG values use the primary GitHub repository and main branch.
Release automation and CI should pass VCS_REF, BUILD_DATE, and VERSION
so labels match the built commit and timestamp.

No change to application behavior; image metadata only.

Co-authored-by: Cursor <cursoragent@cursor.com>
@T012m3n7oR
Copy link
Copy Markdown
Author

I'm not 100% sure where these dockerfiles are utilized to build, but that should at least add the outline for them.

Whatever is building these will need to be updated with correct values for VCS_REF (full SHA), BUILD_DATE (RFC 3339
UTC), and VERSION (tag or git describe) so labels reflect the real build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant