You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The question is, why does it push these 2 extra manifest lists from remote nodes? Is it expected behaviour? Is it documented (I couldn't find it)?
Why I ask: presumably, these extra list.manifest.json prevent Artifactory from removing unreferenced daughter-images when the main list.manifest.json is removed/overwritten.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I'm using docker buildx to build multi-arch images on remote nodes.
Here is how:
As a result, I have 3 list.manifest.json in Artifactory:
Build attestations is disabled:
--provenance=false --sbom=falseWhen I build it locally (without
--builder='remote-ssh-builder') it creates only one list.manifest.json, as expected.The question is, why does it push these 2 extra manifest lists from remote nodes? Is it expected behaviour? Is it documented (I couldn't find it)?
Why I ask: presumably, these extra list.manifest.json prevent Artifactory from removing unreferenced daughter-images when the main list.manifest.json is removed/overwritten.
Thanks
All reactions