If we specify GCP Ubuntu images via packer's source_image_family (vs source_image) we make our builds even less deterministic (they already run apt update && apt upgrade).
I've experienced this in monopacker with my v4l fix for the 2204 images. Kernel 6.8.0 wasn't default in the jammy 'source_image_family' image that I initially pulled, but it is now (which breaks the implemented v4l fix).
Viewing the 'source_image's that the 'source_image_family' points at:
gcloud compute images list --show-deprecated | grep ubuntu-2204-lts
If we specify GCP Ubuntu images via packer's
source_image_family(vssource_image) we make our builds even less deterministic (they already run apt update && apt upgrade).I've experienced this in monopacker with my v4l fix for the 2204 images. Kernel 6.8.0 wasn't default in the jammy 'source_image_family' image that I initially pulled, but it is now (which breaks the implemented v4l fix).
Viewing the 'source_image's that the 'source_image_family' points at:
gcloud compute images list --show-deprecated | grep ubuntu-2204-lts