| Age | Commit message (Collapse) | Author |
|---|
|
This introduces extra validation for WSL image creation to ensure
the result is usable.
|
|
This renames the minimal profile to "tiny", it's useful to have a
profile that builds quickly and provides a small artifact. However, the
minimal name mirrors the Fedora Minimal spin name and might confuse
people building images about what they're actually building.
The Tiny descriptions do not replicate the Fedora Minimal spin.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
|
|
This introduces the beginnings of an image definition for Windows
Subsystem for Linux (WSL).
The package list is based on the core and standard grouplists. Some
packages, like the kernel, dracut, and so on, are omitted as they are
unnecessary. Others, like audit, don't work in the environment. Finally,
many packages are omitted since I thought "people probably won't want
that", so the package list is completely up for debate. This is just a
reasonable starting point that works.
Build/test instructions:
To build the tarball:
$ ./kiwi-build --image-profile=WSL-Base --image-type=tbz --output-dir=./build/
Get it to a Windows host with WSL installed. To boot it with cgroupsv2,
add the following to `.wslconfig` in the Windows host home folder:
[wsl2]
kernelCommandLine=systemd.unified_cgroup_hierarchhy=1 cgroup_no_v1=all
This assumes the latest WSL release is installed, at least version 2.4.4:
$ wsl --install --from-file .\path\to\the\fedora.tar.xz
Alternatively, if you're using something prior to version 2.4.4:
$ wsl --import --version=2 Fedora C:\path\to\storage\Fedora\ .\path\to\the\fedora.tar.xz
Finally, run it with:
$ wsl -d Fedora
If you are using 2.4.4+, you will be prompted for a username and then
dropped into an interactive shell with that user and passwordless sudo
access.
If you're using an older version, you need to do:
$ wsl -d Fedora -u root
# /usr/libexec/wsl/oobe.sh
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
This is an example that can be used for creating small disk images
to verify that the basics work.
|
|
|
|
We only need to preserve the log file anyway.
|
|
Production builds in Fedora have a couple extra features:
* ISOs have custom overrides to set the correct volume/app IDs
* Image filenames are structured to follow roughly NVRA format
Now we support these features with extra helper scripts. If a
"image release" value is passed in, then we fully mimic the
production image build process.
This will be particularly useful for making respins of Fedora images
with updates applied.
|
|
This is loosely based on the Server kickstart and ELN descriptions.
This covers both the disk image for running on ARM hardware as well
as the VM image for running on various hypervisor platforms.
|
|
Add a new definition for a RootFS to be used by FEX (https://src.fedoraproject.org/rpms/fex-emu). This is based on the upstream manifest (https://github.com/FEX-Emu/RootFS/blob/main/Configs/Fedora_40.json).
Signed-off-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
|
|
Larger disk means more IO performance.
Require more CPUs to aid mksquashfs performance.
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
|
|
In preparation for having multiple top-level kiwi description files,
expose the ability to define which file to read.
Additionally, tests are updated to use this new flag.
|
|
This adds a disk image build profile to produce Fedora KDE images.
Additionally, these profiles are now tested in CI.
|
|
This is similar to "ubi-init" on UBI/RHEL side.
Fixes BZ 2278884.
|
|
This incorporates the labels that are expected for Fedora images.
|
|
These are needed for the images currently being validated in CI.
|
|
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
|
|
Once the image build is done, we do not need the working tree
anymore and leaving it around causes it to get archived at the
end of CI runs when it is totally unneeded.
|
|
This adds the definitions for building the container tarballs for
the base container, the minimal base container, and the toolbox
container.
|
|
We now have more than one cloud system that is essentially a KVM
environment that uses cloud-init to boot, so now we declare that
"generic" and have the OpenStack and Oracle images reuse those
definitions.
Also, in preparation for layered cloud image variants, rename
them from "Cloud-" to "Cloud-Base-". Vagrant variants are
similarly prefixed to make it clear who provides them.
Finally, restructure the layout of the tmt plans to match the
description structure.
|
|
This allows us to have pull requests tested before we review changes
to merge.
|
Neal Gompa
Simon de Vlieger
Jeremy Cline
Davide Cavalca
Miroslav Vadkerti
Romain Geissler
Gerd Hoffmann
