Summary
BoxLite boots the statically linked boxlite-guest from a rootfs built from debian:bookworm-slim. This requires an OCI pull, ext4 construction, binary injection, caching, and a per-Box guest-rootfs.qcow2, although the agent does not need Debian userspace.
The guest also depends on external mkfs.ext4, resize2fs, and chown paths. mkfs.ext4 has no production caller, but resize2fs is still used to apply disk_size_gb when creating a Box. This prevents removing the distribution rootfs without first separating those responsibilities.
Scope
Use a minimal directory rootfs containing static boxlite-guest and static e2fsprogs tooling. Remove the Debian guest image and its ext4/QCOW2 bootstrap pipeline, along with the unused guest-side formatting path. Keep the user container rootfs pipeline and current create-time disk_size_gb behavior unchanged.
Growing an existing Box disk remains separate work.
Summary
BoxLite boots the statically linked
boxlite-guestfrom a rootfs built fromdebian:bookworm-slim. This requires an OCI pull, ext4 construction, binary injection, caching, and a per-Boxguest-rootfs.qcow2, although the agent does not need Debian userspace.The guest also depends on external
mkfs.ext4,resize2fs, andchownpaths.mkfs.ext4has no production caller, butresize2fsis still used to applydisk_size_gbwhen creating a Box. This prevents removing the distribution rootfs without first separating those responsibilities.Scope
Use a minimal directory rootfs containing static
boxlite-guestand static e2fsprogs tooling. Remove the Debian guest image and its ext4/QCOW2 bootstrap pipeline, along with the unused guest-side formatting path. Keep the user container rootfs pipeline and current create-timedisk_size_gbbehavior unchanged.Growing an existing Box disk remains separate work.