diskimage-builder/diskimage_builder/elements/opensuse
Andreas Florath 3636b40f74 Introduce manual setting of DIB_INIT_SYSTEM
The current implementation evauates the dib-init-system
script too early.  Also it looks that there is no simple
way of getting the info about the init system automatically:
another element can install (later on) a different
init system.  Therefore the only reliable way of setting
this is manual.

Change-Id: I6e9ffa1bdb3154f488f4fd335b197699b86aacd4
Signed-off-by: Andreas Florath <andreas@florath.net>
2019-11-21 12:38:15 +11:00
..
environment.d Introduce manual setting of DIB_INIT_SYSTEM 2019-11-21 12:38:15 +11:00
extra-data.d Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
root.d Update test coverage for openSUSE/-minimal to 15.0 2019-05-08 14:59:51 +00:00
test-elements Rename openSUSE 15.1 testing to 15 2019-08-30 22:44:40 +02:00
README.rst Update test coverage for openSUSE/-minimal to 15.1 2019-06-13 09:20:40 +02:00
element-deps Clear /etc/machine-id to avoid duplicate machine-ids 2017-08-06 13:56:58 -04:00
element-provides Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
package-installs.yaml Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00

README.rst

opensuse

Use an openSUSE cloud image as the baseline for built disk images. The images are located in distribution specific sub directories under

https://download.opensuse.org/repositories/Cloud:/Images:/

These images should be considered experimental. There are currently only x86_64 images.

Environment Variables

DIB_RELEASE
Required

No

Default

15.1

Description

Set the desired openSUSE release.

DIB_CLOUD_IMAGES
Required

No

Default

https://download.opensuse.org/repositories/Cloud:/Images:/(openSUSE|Leap)_${DIB_RELEASE}

Description

Set the desired URL to fetch the images from.

Notes:

  • There are very frequently new automated builds that include changes that happen during the product maintenance. The download directories contain an unversioned name and a versioned name. The unversioned name will always point to the latest image, but will frequently change its content. The versioned one will never change content, but will frequently be deleted and replaced by a newer build with a higher version-release number.