f6a02fbdb9
dracut has a "hostonly" mode where it builds an initramfs that is suitable for booting the system it is building on. This is on by default, but obviously in our nested multi-platform chroot situation this is fraught with danger. As highlighted by [1] our builds were inadvertently turning off "hostonly" mode when the mountpoints in the chroot were not found. The CentOS 7.3 behaviour change broke this and we ended up with an initramfs with no file-system modules. Iaf2a1e8470f642bfaaaad3f9b7f26cfc8cc445c9 introduced a regeneration of the initramfs, which I think does work as described because it runs in the loopback device. However, dracut includes a package that installs configuration overrides to build a generic initramfs. This is really what we want, and should solve the problem no matter where the initramfs is created. Add this package into yum-minimal and remove the extra re-create call which should not be necessary. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1405238 Change-Id: I5d203f2abe743cb23a44d449850e692a948e7871
yum-minimal
Base element for creating minimal yum-based images.
This element is incomplete by itself, you'll want to use the centos-minimal or fedora-minimal elements to get an actual base image.
Use of this element will require 'yum' and 'yum-utils' to be installed on Ubuntu and Debian. Nothing additional is needed on Fedora or CentOS.
The DIB_OFFLINE or more specific DIB_YUMCHROOT_USE_CACHE variables can be set to prefer the use of a pre-cached root filesystem tarball.
If you wish to have DHCP networking setup for eth0 & eth1 via /etc/sysconfig/network-config scripts/ifcfg-eth[0|1], set the environment variable DIB_YUM_MINIMAL_CREATE_INTERFACES to 1.