381ff6ab1d
Fixes problems found by set -eu and pipefail, including: -Many unset variables -Commands that can fail under normal circumstances, which breaks with set -e. This change swallows those expected errors to allow our existing error code to handle them. -The dkms element was not finding Fedora kernel versions correctly. This may be an issue for other distros too, but since Fedora was working fine without this functionality I only changed it to print a warning message rather than failing the build when it happens. -The ramdisk init script will not be set -eu because if it fails the result is a kernel panic, which can be tricky to debug. However, in testing with set -e a few failing commands were found and have been fixed in this patch. Change-Id: I44cf98dfc80cfcaec54b88cc83be80a3dbf2cec3 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| extra-data.d | ||
| init.d | ||
| install.d | ||
| post-install.d | ||
| README.md | ||
This is the ramdisk element.
Almost any user building a ramdisk will want to include this in their build, as it triggers many of the vital functionality from the basic diskimage-builder libraries (such as init script aggregation, busybox population, etc).
An example of when one might want to use this toolchain to build a ramdisk would be the initial deployment of baremetal nodes in a TripleO setup. Various tools and scripts need to be injected into a ramdisk that will fetch and apply a machine image to local disks. That tooling/scripting customisation can be easily applied in a repeatable and automatable way, using this element.
See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.