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
Chiseled images need base-files_chisel slice to generate the manifest (example usage). Manifest is generated into /var/lib/chisel/manifest.wall file, which is zstd compressed. Uncompressed it's a "jsonwall" file that contains information for various metadata like packages, paths, slices, etc. (example manifest)
For copa, we are probably most interested in the package kinds. Copa should be able to parse each of the package kinds for names and versions. However, I am not sure how would copa should handle the sha256 data since this will be changing.
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.
Activity
sozercan commentedon Oct 1, 2024
hold until new manifest is supported canonical/chisel#148 (comment)
https://github.com/canonical/chisel/releases/tag/v1.0.0 is out now
sozercan commentedon Nov 5, 2024
This is an interesting one. https://discourse.ubuntu.com/t/chisel-manifest-is-supported-in-newly-released-v1-0-0/48944 has the most information about this new format.
Chiseled images need
base-files_chiselslice to generate the manifest (example usage). Manifest is generated into/var/lib/chisel/manifest.wallfile, which is zstd compressed. Uncompressed it's a "jsonwall" file that contains information for various metadata like packages, paths, slices, etc. (example manifest)For copa, we are probably most interested in the
packagekinds. Copa should be able to parse each of thepackagekinds for names and versions. However, I am not sure how would copa should handle thesha256data since this will be changing.github-actions commentedon Jul 4, 2025
This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.