bootstrap-vz is looking for a new home.
The reason is that I am simply not using bootstrap-vz myself very much lately,
so any bugfixes or improvements are currently introduced via PRs only.

If you are willing to take over the project and have a track record with the
Debian community or with the development of software like bootstrap-vz,
kindly let me know by opening an issue that includes some references.
There is a considerable amount of people using the software daily,
and I would love seeing my work being continued.
I will be happy to answer any questions regarding the code future maintainers
might have, now and also in the coming years, so nothing will just be dumped in
your lap :-)

bootstrap-vz is a bootstrapping framework for Debian that creates ready-to-boot
images able to run on a number of cloud providers and virtual machines.
bootstrap-vz runs without any user intervention and
generates images for the following virtualization platforms:

bootstrap-vz has a master branch into which stable feature branches are merged.

After checking out the branch of your choice you can install the
python dependencies by running pythonsetup.pyinstall. However,
depending on what kind of image you’d like to bootstrap, there are
other debian package dependencies as well, at the very least you will
need debootstrap.
The documentation
explains this in more detail.

Note that bootstrap-vz will tell you which tools it requires when they
aren’t present (the different packages are mentioned in the error
message), so you can simply run bootstrap-vz once to get a list of the
packages, install them, and then re-run.

Here are a few quickstart tutorials for the most common images.
If you plan on partitioning your volume, you will need the parted
package and kpartx:

root@host:~# apt-get install parted kpartx

Note that you can always abort a bootstrapping process by pressing
Ctrl+C, bootstrap-vz will then initiate a cleanup/rollback process,
where volumes are detached/deleted and temporary files removed, pressing
Ctrl+C a second time shortcuts that procedure, halts the cleanup and
quits the process.

The resulting image should be no larger than 82 MB (81.95 MB to be exact).
The manifest jessie-minimized.yml uses the
minimize_size plugin to reduce the image
size considerably. Rather than installing docker from the debian main repo
it is recommended to install the latest docker version.

bootstrap-vz tries very hard to clean up after itself both if a run was
successful but also if it failed. This ensures that you are not left
with volumes still attached to the host which are useless. If an error
occurred you can simply correct the problem that caused it and rerun
everything, there will be no leftovers from the previous run (as always
there are of course rare/unlikely exceptions to that rule). The error
messages should always give you a strong hint at what is wrong, if that
is not the case please consider opening an issue and attach
both the error message and your manifest (preferably as a gist or
similar).

Any other requirements are dependent upon the manifest configuration
and are detailed in the corresponding sections of the documentation.
Before the bootstrapping process begins however,
bootstrap-vz will warn you if a requirement has not been met.

bootstrap-vz was coded from scratch in python once the bash script
architecture that was used in the
build-debian-cloud
bootstrapper reached its limits. The project has since grown well beyond
its original goal, but has kept the focus on Debian images.