Lubuntu/livecd-rootfs
3
0
Fork 0
mirror of https://git.launchpad.net/livecd-rootfs synced 2025-03-12 03:41:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Bump UEFI disk image size for amd64 to 3.5 GB

Browse Source 
Current Kinetic GCE image builds are failing with the following error:

update-initramfs: Generating /boot/initrd.img-5.19.0-1004-gcp
zstd: error 25 : Write error : No space left on device (cannot write compressed block)
E: mkinitramfs failure zstd -q -1 -T0 25

Seems like after `linux-gcp` update from 5.15 to 5.19 `linux-modules` package
has gotten ~40MB larger and with that GCE image builds are over the edge wrt
available disk space in chroot.

Bumped up disk image size for amd64 to 3.5GB to match the sizes used by armhf
and generic images.
This commit is contained in:
Ivan Kapelyukhin 2022-09-14 18:56:50 +02:00
parent ee40e951f2
commit 76d794664a
No known key found for this signature in database
GPG Key ID: BD1EB02A07F55E39
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
debian/changelog vendored
View File

@ -1,3 +1,11 @@
livecd-rootfs (2.779) kinetic; urgency=medium
* ubuntu-cpc/hooks.d/base/disk-image-uefi.binary: Bump UEFI disk image
size for amd64 to 3.5 GB.
Current builds are failing because the disk size is not big enough.
-- Ivan Kapelyukhin <ivan.kapelyukhin@canonical.com> Wed, 14 Sep 2022 18:55:20 +0200
livecd-rootfs (2.778) kinetic; urgency=medium
[ Rudra Saraswat ]

4
live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi.binary
View File

@ -21,6 +21,10 @@ case ${PROJECT:-} in
;;
esac
if [ "$ARCH" = "amd64" ]; then
IMAGE_SIZE=3758096384 # bump to 3.5G (3584*1024**2); Since Kinetic amd64 need more then the default 2.2G
fi
if [ "$ARCH" = "armhf" ]; then
IMAGE_SIZE=3758096384 # bump to 3.5G (3584*1024**2); Since Jammy armhf need more then the default 2.2G
fi