a72645f431
dracut has a loop [1] where it probes top-level directories, tries to find what block device they are on, then determines the file-system of that block device. It then puts those file-system modules into the initramfs for boot. Since we install the kernel package during the chroot phase, / there is not a block device and thus this loop matches nothing and we end up with no file-system modules in the initramfs. This results in a very annoying silent boot hang. By moving re-generation of dracut into finalise.d phase, we run inside the final image where / is the loop-device; the root file-system gets detected correctly and the ext4 module is included correctly. [1] http://git.kernel.org/cgit/boot/dracut/dracut.git/tree/dracut.sh?h=RHEL-7#n1041 Change-Id: Iaf2a1e8470f642bfaaaad3f9b7f26cfc8cc445c9 Signed-off-by: Paul Belanger <pabelanger@redhat.com> |
||
|---|---|---|
| .. | ||
| finalise.d | ||
| install.d | ||
| pre-install.d | ||
| root.d | ||
| element-deps | ||
| package-installs.yaml | ||
| pkg-map | ||
| README.rst | ||
=========== 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`.