
Historically Debian cloud images included backports sources by default (apparently to ensure that new enough cloud-init could be installed to boot on various clouds). DIB mimicked this behavior and included backports by default in the debian-minimal element. Since then packaging for cloud-init has changed and now upstream cloud images no longer include backports by default. Update debian-minimal to match. Users of debian-minimal can include backports again by setting the DIB_APT_SOURCES_CONF variable in their builds. Or they can add the source as a separate source.list.d entry with custom elements. As part of this change the debootstrap element docs are also updated to reflect the change. One thing that was noticed is that the ubuntu-minimal element uses different variables to manage the apt sources despite relying on the common framework from the debootstrap element. The debootstrap docs are updated to include a note about this difference. Change-Id: Id9f0cacf7707709829e49006d26d6c98dc8a8ba5 Signed-off-by: Clark Boylan <clark.boylan@gmail.com>
debian-minimal
The debian-minimal
element uses debootstrap for
generating a minimal image.
By default this element creates the latest stable release. The exact
setting can be found in the element's environment.d
directory in the variable DIB_RELEASE
. If a different
release of Debian should be created, the variable
DIB_RELEASE
can be set appropriately.
Note that this element installs systemd-sysv
as the init
system
The element obeys the DIB_DISTRIBUTION_MIRROR
argument
for mirroring (see debootsrap
element documentation).
However, the security repositories are separate for Debian, so we can
not assume they exist at DIB_DISTRIBUTION_MIRROR
. If you do
not wish to use the upstream repository (from
security.debian.org
) override it with
DIB_DEBIAN_SECURITY_MIRROR
. The security suite name's
subpath can also be overridden to something other than
/updates
with the DIB_DEBIAN_SECURITY_SUBPATH
variable.