-
Notifications
You must be signed in to change notification settings - Fork 401
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
Chainguard annotations are, but should not be, propagated to multi-platform manifest #1231
Comments
if you don't specify the base image that you want to use in your ko build it will use a default one which is |
This is not a question. This is a bug. The problem is not the annotations that identify the base image. The problem is the other annotations. |
This issue is stale because it has been open for 90 days with no |
Reopen, eg. chainguard labels mixed in with my labels "Labels": {
"org.opencontainers.image.authors": "Chainguard Team https://www.chainguard.dev/",
"org.opencontainers.image.created": "2024-09-09T05:27:49Z",
"org.opencontainers.image.licenses": "MIT",
"org.opencontainers.image.revision": "f97aa24922679eeabdf6d9e4b219c7cd889b4685",
"org.opencontainers.image.source": "https://github.com/phi-ag/mta-sts-exporter",
"org.opencontainers.image.url": "https://images.chainguard.dev/directory/image/static/overview",
"org.opencontainers.image.vendor": "Chainguard",
"org.opencontainers.image.version": "1.7.36"
} |
This adds a new build flag for setting annotations on image indexes and manifests. Annotations are no longer copied from the base image. `org.opencontainers.image.base.digest` and `org.opencontainers.image.base.name` are always set to the resolved values. Usage example: ```sh ko build --image-annotation foo=bar,fizz=buzz . ``` Fixes ko-build#1090 Fixes ko-build#1090 Fixes ko-build#1231 Fixes ko-build#1235 Fixes ko-build#1395
This adds a new build flag for setting annotations on image indexes and manifests. Annotations are no longer copied from the base image. `org.opencontainers.image.base.digest` and `org.opencontainers.image.base.name` are always set to the resolved values. Usage example: ```sh ko build --image-annotation foo=bar,fizz=buzz . ``` Fixes #1090 Fixes #1090 Fixes #1231 Fixes #1235 Fixes #1395
When I
ko build
a multi-platform manifest, my manifest ends up with annotations attributing it to chainguard. Here is what I found:The text was updated successfully, but these errors were encountered: