870374c8da
dib_[environment|args] manifest files are currently generated by the base element and then moved by the manifest element. This creates too many corner cases -- if you don't include the base element (we are trying to empty it ATM) you don't get the env/args saved at all; if you include base but don't include the manifest element they're saved to /etc, but if you do have the manifest element they're moved to the manifest dir. Move generation of these into the manifest element directly and update the documentation to reflect this. In practice this doesn't change things, because the "manifests" element gets pulled in via deps for most builds. Change-Id: I3f23037058137d166b29f0b70fd1a02c22c07fc8 Signed-off-by: Andreas Florath <andreas@florath.net> |
||
---|---|---|
.. | ||
cleanup.d | ||
environment.d | ||
install.d | ||
pre-install.d | ||
root.d | ||
element-deps | ||
package-installs.yaml | ||
pkg-map | ||
README.rst |
==== base ==== This is the base element. Almost all users will want to include this in their disk image build, as it includes a lot of useful functionality. The `DIB_CLOUD_INIT_ETC_HOSTS` environment variable can be used to customize cloud-init's management of `/etc/hosts`: * If the variable is set to something, write that value as cloud-init's manage_etc_hosts. * If the variable is set to an empty string, don't create manage_etc_hosts setting (cloud-init will use its default value). * If the variable is not set, use "localhost" for now. Later, not setting the variable will mean using cloud-init's default. (To preserve diskimage-builder's current default behavior in the future, set the variable to "localhost" explicitly.) Notes: * If you are getting warnings during the build about your locale being missing, consider installing/generating the relevant locale. This may be as simple as having language-pack-XX installed in the pre-install stage * This element ensures /tmp/ccache will be available in the chroot during the root, extra-data, pre-install, install and post-install stages. /tmp/ccache is unavailable during block-device, finalise and cleanup stages as it will have been automatically unmounted by then.