a0f747932d
Debian Stretch released as stable recently, and the init system is less tightly specified in the base dependencies (for some info, see [1]). It seems, probably unintentionally, that in the previous release systemd-sysv was brought in by debootstrap, but that is no longer happening. Add systemd as an early dependency of debian-minimal. Remove the package-installs.yaml as that happens too late (other things need to know the init system to write out service files, etc and probe for systemd utils before package-installs). As mentioned, I do not believe the "only install systemd on testing" idea was actually working here, because it was being brought in during the initial debootstrap. Update some documentation to explain what's going on [1] https://lists.debian.org/debian-boot/2015/05/msg00156.html Change-Id: Id67c0cf08728407d234976f9807d3bd71d12f758
17 lines
569 B
ReStructuredText
17 lines
569 B
ReStructuredText
==============
|
|
debian-minimal
|
|
==============
|
|
|
|
The ``debian-minimal`` element uses debootstrap for generating a
|
|
minimal image. In contrast the ``debian`` element uses the cloud-image
|
|
as the initial base.
|
|
|
|
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
|
|
|
|
.. element_deps::
|