BtrFS support

[thomastthai]

BtrFS support

[jonathanmarchuot]

This is also currently a headache of mine -- patching Ubuntu images that Libre Computer is publishing with btrfs supported. I would love to see btrfs resizing supported by the project in the future!

Currently, the way I've found around this, is by making sure your json gets rid of the "target_image_size", and then resize your source image prior to running packer.

truncate --size=+1400M ./original.img

sudo losetup --show -f -P ./original.img
#	'/dev/loop3'

sudo parted /dev/loop3
#	'print'
#		Disk /dev/loop3: 7213MB
#		part 2 end 2809MB size 2540MB
#
#      ((take the disk size '7213' above, then resize the partition to take the full space))
#	'resizepart 2'
#		End?  [2809MB]?
#		'7213MB'
#
#	'print'
#		Disk /dev/loop3: 7213MB
#		part 2 end 7213MB size 6944MB
#
#	'quit'

sudo mkdir -p /btrfs
sudo mount /dev/loop3p2 /btrfs

sudo btrfs filesystem resize max /btrfs
sudo btrfs filesystem show
sudo btrfs check --force /dev/loop3p2

sudo umount /btrfs
sudo losetup -d /dev/loop3

shasum -a 256 ./original.img

And then take your "new" original.img with your new shasum and run packer against that. Good luck!

[thomastthai]

@jonathanmarchuot, thanks for sharing your workaround!

Does your root partition come with btrfs as default?

For the Raspberry Pi Bookworm, I manually convert the factory image's root partion from ext4 to btrfs. I haven't found an automated way to do that conversion via Vagrant and Packer.

Are you doing the workaround manually or automated via code?