| Age | Commit message (Collapse) | Author |
|---|
|
This lets us free up the space allocated for the partition and gives
us dynamically allocated space for boot data like we have with the
rest of the operating system.
We do not do this for s390x because zipl does not support it.
Reference: https://fedoraproject.org/wiki/Changes/BtrfsBootForCloud
|
|
The Fedora LXDE spin does not have a fedora-release variant,
so the image build fails when trying to request one.
This is an error in fedora-release and will (hopefully) be eventually
fixed. For now, disable the block requesting it so we can restore it
later.
|
|
Since`rootfiles` now uses systemd-tmpfiles to install dotfiles under
root folder instead of copying.
|
|
Since`rootfiles` now uses systemd-tmpfiles to install dotfiles under
root folder instead of copying.
|
|
Wine in Fedora 43 is built with WoW64 which supports running 32-bit
Windows applications with 64-bit wine build.
While this might cause regressions in some corner cases it reduces the
image size considerably. The xz compressed erofs image shrank from
~1090MB to ~933MB.
|
|
Those are no longer needed. The system mesa contains fully functioning
asahi OpenGL/Vulkan drivers so there is no need to provide older
llvm-libs and clang-libs for mesa overlays.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
With the increase in content in initramfs, a long-overdue raise
of the default size for /boot is warranted.
Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition
|
|
With the increase in content in initramfs, a long-overdue raise
of the default size for /boot is warranted.
Reference: https://fedoraproject.org/wiki/Changes/2GbootPartition
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
This ensures that there's empty space for arm-image-installer to
inject firmware blobs into images as part of preparing to install
for various single board computers.
|
|
nss-mdns is not included in RHEL, and mesa-vulkan-drivers is x86_64 only.
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
WSL does not support SELinux, so at best it's pointless to install. This
also actively breaks WSL 1 users, although I don't think we should
suggest that we support that, and if the policy on the builder doesn't
match the target things break during the build.
It also reduced the build time from ~80 seconds to ~70 seconds for me,
so that's nice.
See: 39b379f7d ("wsl: drop the SELinux packages from the WSL base image")
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
WSL does not support SELinux, so at best it's pointless to install. This
also actively breaks WSL 1 users, although I don't think we should
suggest that we support that, and if the policy on the builder doesn't
match the target things break during the build.
It also reduced the build time from ~80 seconds to ~70 seconds for me,
so that's nice.
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
The anaconda-webui package is now installed by default for live
media, so these are no longer necessary.
|
|
|
|
This reverts commit 24c4fc39c2995e12610173acfdce689497a84120.
With a PR we can run the tests on openQA staging, identify any
problems with the change, and extend the tests to cover the
additional screens that show up with KDE.
|
|
This reverts commit e4d801674c86b0675f0ff6fed8c8fee0e5e47546.
openQA has not yet been prepared for this change and it is
causing all updates to fail gating. We need to prepare the tests
before merging this.
|
|
While the Web UI is still missing two features outlined in the Change Proposal [1], enabling it
early will help identify additional issues and improve integration. The missing features are:
- Date/Time Configuration Screen (currently implemented by GIS in Workstation)
- Configurable Browser Support (currently hardcoded to Firefox)
[1] https://fedoraproject.org/wiki/Changes/AnacondaWebUIforFedoraSpins#Detailed_Description
|
|
Fixes https://github.com/fedora-cloud/docker-brew-fedora/issues/119
Signed-off-by: Clement Verna <cverna@tutatnota.com>
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
The serial device name on Arm is ttyAMA, not ttyS. This splits the
configuration for ELN images based on the architecture and adjusts the
kernel command line.
Note that prior to this change, aarch64 would still output kernel logs
to the ttyAMA0 console (on Azure, at least) due to the ACPI SPCR table.
On aarch64 the console in this table, if it's present, is _always_
configured as the kernel's default console. However, systemd logs would
not be sent to the serial console because it seems it was honoring the
kernel command line configuration which had ttyS0 as the default.
Note: this is the exact same change as 4979662a547e ("Cloud: Adjust
aarch64 images to use the correct serial console"), if you're reverting
this, you probably want to also revert that one.
Also see: https://pagure.io/cloud-sig/issue/394
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1661288
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
The serial device name on Arm is ttyAMA, not ttyS. This splits the
configuration for Cloud images based on the architecture and adjusts the
kernel command line.
Note that prior to this change, aarch64 would still output kernel logs
to the ttyAMA0 console (on Azure, at least) due to the ACPI SPCR table.
On aarch64 the console in this table, if it's present, is _always_
configured as the kernel's default console. However, systemd logs would
not be sent to the serial console because it seems it was honoring the
kernel command line configuration which had ttyS0 as the default.
Also see: https://pagure.io/cloud-sig/issue/394
Also see: https://bugzilla.redhat.com/show_bug.cgi?id=1661288
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
This introduces extra validation for WSL image creation to ensure
the result is usable.
|
|
This introduces extra validation for WSL image creation to ensure
the result is usable.
|
|
This will be used by toolbox(1) to ensure that the certificates from
certificate authorities (or CAs) that are available inside a Toolbx
container are kept synchronized with the host operating system [1]. Any
program that uses PKCS #11 to access CA certificates should see the same
ones both inside the container and on the host.
This is the same approach taken by Flatpak [2].
[1] https://github.com/containers/toolbox/issues/626
[2] Flatpak commit 66b2ff40f7caf3a7
https://github.com/flatpak/flatpak/commit/66b2ff40f7caf3a7
https://github.com/flatpak/flatpak/pull/1757
https://github.com/p11-glue/p11-kit/issues/68
https://pagure.io/fedora-kiwi-descriptions/pull-request/189
|
|
The p11-kit RPM is neither explicitly mentioned in the list of default
RPMs on Fedora Silverblue and Workstation [1], nor was it explicitly
installed by the Container/Dockerfile equivalent of the fedora-toolbox
OCI images [2].
The Container/Dockerfile listed p11-kit as one of the RPMs that had to
be reinstalled, because it was inherited from the fedora base image, and
had its documentation and translations stripped out. The reinstallation
would be skipped if for some reason it was no longer part of the fedora
base image.
This was misinterpreted when creating the Kickstart equivalent of the
fedora-toolbox OCI images [3] and that's how it ended up in the KIWI
description.
In reality, p11-kit gets pulled in as a dependency of ca-certificates,
gnutls, etc. and that's sufficient.
Fallout from d27e4c3f6c3e13bcefe9d1d904386794140d8a91
[1] https://pagure.io/fedora-comps/
[2] https://src.fedoraproject.org/container/fedora-toolbox
[3] fedora-kickstarts commit 48e2c3b5598de32f
https://pagure.io/fedora-kickstarts/c/48e2c3b5598de32f
https://pagure.io/fedora-kickstarts/pull-request/964
https://pagure.io/releng/issue/11399
https://pagure.io/fedora-kiwi-descriptions/pull-request/189
|
|
Although we include curl, some folks expect wget. Also, one of the more
common uses of WSL is in combination with VS Code, and its setup script
on remote hosts uses wget.
Signed-off-by: Jeremy Cline <jeremycline@linux.microsoft.com>
|
|
Signed-off-by: Troy Dawson <tdawson@redhat.com>
|
|
This became necessary with 10.0.13 / after merging
https://github.com/OSInside/kiwi/pull/2535 but doesn't seem to
noticeable effects besides miisin "GRUB_ENABLE_BLSCFG=true" in
/etc/default/grub.
|
|
Fixes https://pagure.io/fedora-kiwi-descriptions/issue/169,
https://bugzilla.redhat.com/show_bug.cgi?id=2355948.
|
|
This is needed for XUL-based applications to work (for example, Zotero).
Signed-off-by: Davide Cavalca <dcavalca@fedoraproject.org>
|
|
It can be useful to have access to `setfiles` inside a `toolbx`
container. Especially when using them as bootstrap roots to setup
other trees.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
|
|
If $PATH is not set, we get the default from crun [1]:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
This is not useful, because in the image, /bin, /sbin, /usr/sbin are all
symlinks. /usr/local/sbin does not exist.
When /usr/sbin is a symlink to /usr/bin, and we use have a $PATH with
/usr/sbin before /usr/bin, various tools will discover /usr/sbin/foo when
looking for 'foo' [2], which is confusing and ugly.
[1] https://github.com/containers/crun/blob/a980c89665bb488ff206e47e9083f75b48528714/src/libcrun/container.c#L183
[2] https://src.fedoraproject.org/rpms/setup/pull-request/18#comment-253719
Co-authored-by: Simon de Vlieger <cmdr@supakeen.com>
|
|
|
|
We have pypy3.11.
pypy3.9 was retired.
See https://bugzilla.redhat.com/2348737
|
|
The Raspberry Pi 3 does not recognize a FAT filesystem marked with
the 0xef type, so until we drop support for this device, hack the
partition manually to use a legacy FAT filesystem partition type.
|
|
Now that we have a lot more stuff installed in the ESP, we need
the ESP to be bigger. This matches the size used for the desktop
disk variants.
|
|
It is hard to ensure that hardware support packages are pulled in
universally when it's splintered across different variant profiles.
To fix this and ensure Server benefits from this, unify everything
into a common profile and make everything require it.
|
|
U-Boot does not support XFS and this causes significant issues
when trying to boot Fedora Server on single board computers.
Resolve this by using ext4 here, as all U-Boot variants generally
support this.
|
|
Turns out that different boards needs different values, so
hardcoding a specific one here is not a good idea. Luckily,
Linux can usually figure things out on its own and automatically
provide a working serial console.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
|
|
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 is a tiny package (250kB) that seems to be a relatively common
dependency (it just provides error codes and some common helpers, used
by stuff other than gpg itself).
|
|
Most of the changes are self-explanatory and just follow what's
already happening for existing architectures.
Two things are worth pointing out:
* we need to use shim-unsigned instead of shim-signed because
riscv64 is not fully integrated into Fedora yet and so we
can't do Secure Boot signing for the time being;
* we use ext4 as bootfilesystem since in most cases the
underlying firmware is going to be U-Boot, which needs to be
able to load the board's DTB from /boot and doesn't support
XFS.
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.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 ported over from the kickstart definitions.
|
|
While cloud images can usually be booted without any issues and
for workstation installs we want a visually polished experience,
in the case of server installs on real hardware it is generally
expected to have convenient access to the bootloader menu for
troubleshooting purposes.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
|
|
This avoids a dependency on the full systemd package for non-init
containers.
|
Neal Gompa
jackyzy823
Janne Grunau
Troy Dawson
Yaakov Selkowitz
Jeremy Cline
Katerina Koukiou
Adam Williamson
Clement Verna
Debarshi Ray
Jan Pazdziora
Davide Cavalca
Simon de Vlieger
Zbigniew Jędrzejewski-Szmek
Allan
Miro Hrončok
Andrea Bolognani
Asahi Lina
David Abdurachmanov
Jeremy Cline
