Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should we / how should we link binary images to this source repo #73

Open
jmtd opened this issue Feb 27, 2019 · 1 comment
Open

should we / how should we link binary images to this source repo #73

jmtd opened this issue Feb 27, 2019 · 1 comment

Comments

@jmtd
Copy link
Member

jmtd commented Feb 27, 2019

Should we add a label that points containers built from this repository back to it? Maybe populate vcs-url as per https://github.com/projectatomic/ContainerApplicationGenericLabels

For Red Hat Product images, vcs-ref is populated by our build system, but I don't think the ref maps back to this repository, but to the intermediate build repository where assets are collated for reproducible building.

@jmtd
Copy link
Member Author

jmtd commented Aug 30, 2023

Should we add a label that points containers built from this repository back to it? Maybe populate vcs-url as per https://github.com/projectatomic/ContainerApplicationGenericLabels

That URI points at a dead project.

This is a similar thing with traction: https://specs.opencontainers.org/image-spec/annotations/

we could set org.opencontainers.image.source

For Red Hat Product images, vcs-ref is populated by our build system, but I don't think the ref maps back to this repository, but to the intermediate build repository where assets are collated for reproducible building.

Confirmed. so setting vcs-url would not be useful since it would conflict with the data in vcs-ref.

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

No branches or pull requests

1 participant