separately, on the isos we used to run /usr/lib/snapd/snap-preseed to speed up first boot and snap startup.
Ideally we should still run that for the canary image with asserted-signed classic model.
The questions are if this is possible and how to do it specifically:
1) can we run /usr/lib/snapd/snap-preseed on the asserted-signed classic model system?
2) will that generate something else (like a tarball?) rather than lots of files in /var/lib/snapd like it was with legacy style unsigned classic models?
3) does the result of /usr/lib/snapd/snap-presseed require signing? If yes, how, and can it be done post-build? (i.e. livefs builder will not currently have access to the signing key)
separately, on the isos we used to run /usr/lib/ snapd/snap- preseed to speed up first boot and snap startup.
Ideally we should still run that for the canary image with asserted-signed classic model.
The questions are if this is possible and how to do it specifically:
1) can we run /usr/lib/ snapd/snap- preseed on the asserted-signed classic model system? snapd/snap- presseed require signing? If yes, how, and can it be done post-build? (i.e. livefs builder will not currently have access to the signing key)
2) will that generate something else (like a tarball?) rather than lots of files in /var/lib/snapd like it was with legacy style unsigned classic models?
3) does the result of /usr/lib/