From 56234333f397eedf785b6983709989aaceddb4f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz=20=27sil2100=27=20Zemczak?= Date: Fri, 6 Sep 2019 11:55:33 +0200 Subject: [PATCH] Add explaination to why ubuntu-image == device image. --- .../hooks.d/chroot/999-ubuntu-image-customization.chroot | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/live-build/ubuntu-cpc/hooks.d/chroot/999-ubuntu-image-customization.chroot b/live-build/ubuntu-cpc/hooks.d/chroot/999-ubuntu-image-customization.chroot index d1e89bae..ad4b3499 100755 --- a/live-build/ubuntu-cpc/hooks.d/chroot/999-ubuntu-image-customization.chroot +++ b/live-build/ubuntu-cpc/hooks.d/chroot/999-ubuntu-image-customization.chroot @@ -3,6 +3,11 @@ . /root/config/common # Specific ubuntu-image chroot configuration goes here. +# Currently the ubuntu-image IMAGEFORMAT is equivalent to building an image +# for a physical device, not a cloud instance. For such images we want some +# special cloud-init configuration that should not be happening for cloud +# cases. This check should be changed to a per-MODEL/per-SUBARCH check once +# we support building cloud images via ubuntu-image. if [ "$IMAGEFORMAT" == "ubuntu-image" ]; do # If the cloud does not provide a meta-data service this should be run # This will setup a nocloud datasource on the boot partition.