History

Ian Wienand 12b60c4088 Mount /sys RO As noted inline, this works around potential issues by being a strong indication you are in a container (e.g. [1]). Since nothing should be changing anything on the host/build system, this is a generically safer way to operate. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1975588 Change-Id: Ic6802c4ffc2e825f129af10717860a2d1770fe80		2021-07-05 11:45:02 +10:00
..
binary-deps.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
init.d	Mount /sys RO	2021-07-05 11:45:02 +10:00
install.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
post-install.d	Remove use of 'which'.	2017-05-19 12:43:36 -07:00
README.rst	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
element-deps	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
pkg-map	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00

README.rst

ramdisk

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.

NOTE: ramdisks require 1GB minimum memory on the machines they are booting.

See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.