Comment 13 for bug 2052789

Verified Jammy:

Steps:

1. using bartender, built an image using the livecd-rootfs 2.765.41 code pulled from https://launchpad.net/ubuntu/+source/livecd-rootfs/2.765.41

bartender \
--hook-extras-branch jammy \
--livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-rootfs/2.765.41/livecd-rootfs \
--build-provider aws \
--aws-keypair-name ${AWS_BUILD_KEY} \
--aws-profile image_builder \
-- \
--series jammy \
--project ubuntu-cpc \
--image-target qcow2

### NOTE ###
You don't have to provide hook-extras-branch build a qcow2. I just default to always using it...

2. untarred the contents
3. launched with QEMU
qemu-system-x86_64 \
-cpu host -machine type=q35,accel=kvm -m 2048 \
-nographic \
-snapshot \
-netdev id=net00,type=user,hostfwd=tcp::2222-:22 \
-device virtio-net-pci,netdev=net00 \
-drive if=virtio,format=qcow2,file=livecd.ubuntu-cpc.img \
-cdrom cloud_init.iso \
-bios /usr/share/OVMF/OVMF_CODE.fd

### NOTE ###
cloud-init.iso just adds my ssh key into the image.

4. logged in and ran `sudo snap debug seeding`
sudo snap debug seeding
seeded: true
preseeded: true
image-preseeding: 8.498s
seed-completion: 1.823s

5. and just to double check, yes there are snaps

snap list
Name Version Rev Tracking Publisher Notes
core20 20240111 2182 latest/stable canonical✓ base
lxd 5.0.3-babaaf8 27948 5.0/stable/… canonical✓ -
snapd 2.61.2 21184 latest/stable canonical✓ snapd