summaryrefslogtreecommitdiff
path: root/scripts/packer-scripts
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2026-07-16 21:01:50 +0200
committerChristian Breunig <christian@breunig.cc>2026-07-16 22:52:17 +0200
commit3db21e81c99ae1e8bf8f24450046c18f53d78d74 (patch)
tree75be7eff51be43ac1fa6b72ddf9ac9be0bd8b6a4 /scripts/packer-scripts
parent5e2e9a3375a0ec3845822702fb255ac03e2b661f (diff)
downloadvyos-build-3db21e81c99ae1e8bf8f24450046c18f53d78d74.tar.gz
vyos-build-3db21e81c99ae1e8bf8f24450046c18f53d78d74.zip
sbom: T9098: syft should run un squashfs instead of unpacked chroot
lb (live-build) binary runs binary_rootfs first, then binary_grub-efi. binary_grub-efi temporarily installs EFI tooling and then runs: "apt remove --auto-remove --purge --allow-remove-essential" That cleanup is safe for the already-generated squashfs, but it mutates build/chroot and can remove vyos-1x, breaking subsequent work that expects chroot to remain intact for SBOM generation. But why unpacking the squashfs? In an ideal world we could call syft on the compressed squashfs file which is supported. In our world, we do use a BCJ pre-filter chained with LZMA2 for compressing the squashfs, which will increase the compression ratio without a decompression penalty. Difference: ~14.3 MB, ~2.7% smaller This is unsupported by fyft which means we do need to unpack the squashfs first before checking the files and generating the SBOM file.
Diffstat (limited to 'scripts/packer-scripts')
0 files changed, 0 insertions, 0 deletions