-
Notifications
You must be signed in to change notification settings - Fork 55
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
Pushing multiple container images clobbers build metadata values #1099
Labels
jira
For syncing to JIRA
Comments
Why not simply make |
e.g.
|
Unfortunately, we can't change existing types because it would render existing Putting my proposal in JSON: {
...
"base-oscontainer": {
"image": "...",
"digest": "...",
"tags": [...],
"additional-images": [
{
"image": "...",
"digest": "...",
"tags": [...]
},
...
]
},
} |
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 11, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 14, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 14, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 14, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 17, 2025
In coreos/fedora-coreos-pipeline#1091 we added the possibility of publishing container images to multiples repositories. This needs to be reflected in the schema otherwhise we only record one image (currenlty the last pushed). Add a `primary-image` key that extends image by adding an `additional-images` array. Use that for relevant container images objects. See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 17, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 17, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 17, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
jbtrystram
added a commit
to jbtrystram/coreos-assembler
that referenced
this issue
Mar 20, 2025
in coreos/fedora-coreos-pipeline#1091 we started publishing container images in multiples repos. However the build.json was not reflecting that, only storing the last pushed image data, overwriting it with each arch. See coreos#4038 See coreos/fedora-coreos-pipeline#1099
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now in OCP we're pushing the rhel-9.6 image to both Quay.io and registry.ci using the new capabilities added in #1091. The problem is that the cosa schema only supports specifying a single pushed repository. But ideally we include all of them and not just the last one in the list (which is what currently happens).
The relevant part of the schema is here: https://github.com/coreos/coreos-assembler/blob/837190dffb5d5cc56b9815ff937a6196eeb4205e/src/v1.json#L50-L87.
I think probably the cleanest, even though it's still awkward, is to add a
primary-image
object to the schema which sources theimage
object's properties, but also adds a newadditional-images
property. This property is then a list type ofimage
objects.And then in
cosa push-container-manifest
, if the primary object already exists for the image we're pushing, add it to theadditional-images
list in that object instead.The text was updated successfully, but these errors were encountered: