d65678678e
Move dib-run-parts from dib-utils into diskimage-builder directly. For calling outside the chroot, we provide a standard entry-point script. However, as noted in the warning comment, the underlying script is still copied directly into the chroot by the dib-run-parts element. I believe this to be the KISS approach. This removes the dependency on dib-utils. We have discussed this previously and nobody seemed to think retiring dib-utils was going to be an issue. This also updates the documentation to not mention dib-utils, or using disk-image-create via $PATH setup, but rather gives instructions on installing from pip with a virtualenv. Change-Id: Ic1e22ba498d2c368da7d72e2e2b70ff34324feb8
1.3 KiB
Installation
If your distribution does not proivde packages, you should install
diskimage-builder via pip, mostly likely in a
virtualenv to keep it separate.
For example, to create a virtualenv and install from
pip
virtualenv ~/dib-virtualenv
. ~/dib-virtualenv/bin/activate
pip install diskimage-builderOnce installed, you will be able to build images
<building_an_image> using disk-image-create
and the elements included in the main diskimage-builder
repository.
Requirements
Most image formats require the qemu-img tool which is
provided by the qemu-utils package on Ubuntu/Debian or the
qemu package on Fedora/RHEL/opensuse/Gentoo.
Some image formats, such as VHD, may require additional
tools. Please see the disk-image-create help output for
more information.
Individual elements can also have additional dependencies for the build host. It is recommended you check the documentation for each element you are using to determine if there are any additional dependencies. Of particular note is the need for the dev-python/pyyaml package on Gentoo hosts.
Package Installation
On Gentoo you can emerge diskimage-builder directly.
emerge app-emulation/diskimage-builder