diskimage-builder/diskimage_builder/elements/debootstrap/element-deps

dpkg
modprobe
pkg-map
sysprep
Split the debootstrap functions into an element debootstrap is not debian or ubuntu specific. We can make a debootstrap element that knows how to do all of the things, and then a debian-minimal and ubuntu-minimal image that use it. Finally, make the debian element simply be a collection of the extra things we do to make it look like a cloud-init based cloud image. Change-Id: Iaf46c8e61bf1cac9a096cbfd75d6d6a9111b701e 2015-03-22 20:11:55 +00:00			`dpkg`
Allow debootstrap to cleanup without a kernel Currently there's more-or-less an assumption that a kernel is installed, so module blacklists are simply echoed into the modprobe blacklist. This may not be the case with some ongoing container work. Although we don't need to blacklist modules for containers, it also doesn't hurt. Move the debootstrap element to the new modprobe element, and allow it to create the blacklist directory. Change-Id: I0f057caf473951df56a2af9633e3a5b53e0809b1 2018-09-24 07:34:22 +00:00			`modprobe`
Add cloud-initramfs-growroot for Precise Add a pkg-map to install cloud-initramfs-growroot on Precise, as it is required there because the kernel is too old to use growroot on a live file-system. This was generically removed in e23b087505b85ae1da11054aa980a956f2ec7195. Change-Id: I5e6cbc4b74dc72a6f23f73a018c028f3ff7c0157 2016-05-20 04:32:41 +00:00			`pkg-map`
Ensure machine-id is not included in images Two bugs are addressed. 1) The sysprep element was broken in that it only truncates /etc/machine-id, but not /var/lib/dbus/machine-id. systemd will not generate a new machine-id if /var/lib/dbus/machine-id is present[1], it will simply copy it to /etc/machine-id. We observed machine-ids being packaged in /var/lib/dbus/machine-id on several distros: Ubuntu Bionic, Fedora 29, Debian Stretch. CentOS 7 and Ubuntu Xenial do not contain packaged machine-id as far as I can tell. All test builds were performed using -minimal elements. 2) A second bug existed where debian-minimal did not run the sysprep element at all, so a stretch image I tested contained a populated /etc/machine-id AND a populated /var/lib/dbus/machine-id. [1] https://www.freedesktop.org/software/systemd/man/machine-id.html#Initialization Change-Id: Ibb28b6e90d966a845de38a2cd5a1e8babd2604bc 2019-09-20 03:10:55 +00:00			`sysprep`