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
Along side the StackerContentsAnnotation, it would be nice to have a LayerContentsAnnotation = "com.cisco.layer_contents", which is a list (maybe in json format) of the layer contents. This is especially easy for stacker to generate since in the btrfs backend it has the mtree information, and in the overlay backend it has the overlay/ directory with exactly the contents.
One question here is what to do about whiteouts. I see two possible options:
have the json object be a map, so {"contents": ["/usr/bin/..."], "whiteouts": ["/etc/config.conf"]}, with a list of the whiteouts
generate filenames as in the oci spec, so .wh.foo
Either option will require some processing of the contents of the mtree/overlay, so it's probably down to whichever is easier for tools/humans to consume.
The text was updated successfully, but these errors were encountered:
Along side the StackerContentsAnnotation, it would be nice to have a LayerContentsAnnotation = "com.cisco.layer_contents", which is a list (maybe in json format) of the layer contents. This is especially easy for stacker to generate since in the btrfs backend it has the mtree information, and in the overlay backend it has the overlay/ directory with exactly the contents.
One question here is what to do about whiteouts. I see two possible options:
{"contents": ["/usr/bin/..."], "whiteouts": ["/etc/config.conf"]}
, with a list of the whiteouts.wh.foo
Either option will require some processing of the contents of the mtree/overlay, so it's probably down to whichever is easier for tools/humans to consume.
The text was updated successfully, but these errors were encountered: