The server images don't include container tooling, so attempting
to configure it is not going to work.
In any case, this would be better handled either by patching
the relevant packages or by documenting the necessary steps in
the wiki.
Note that, while toolbox really needs the configuration, podman
works out of the box as long as the image you're trying to run
comes with a riscv64 variant.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
We want our image to be as close as possible to the official
ones, which don't have this. Some of the information is not
accurate anyway.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
The custom repos are shipped as part of the modified fedora-repos
package now, so doing this in config.sh is no longer needed.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
These are the same as other architecture, with a notable
difference: ext4 is used instead of xfs for the boot filesystem.
This is needed because u-boot, which is used as the firmware on
most hardware, only supports the former.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
The use of symlinks is an effective way to convince kiwi to use
the riscv64 repos instead of the regular Fedora ones, but it's
clearly a borderline unmaintainable kludge.
Thankfully we can handle things a lot better by taking advantage
of the fact that repos can be defined per-arch.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Same as in previous commit. This showed up while building default cloud
image. We need a better way to solve this later on.
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
These changes are only needed on physical hardware there we don't have
enough memory and potentially RNG.
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>
(cherry picked from commit 8203a65b0c0e347efb0de9b56a1410d77f2f6486)
We want to build Fedora 41 images, so we need to change these
values back.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
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>
Disk images are usually flashed to media which is much larger
than they are, and all that additional space goes unused until
the user intervenes.
Configure things so that systemd-repart, which runs by default,
automatically takes care of resizing the root partition.
systemd-growfs, which also runs by default, will subsequently
take care of resizing the filesystem to fill the newly-enlarged
partition.
Note that we don't do this for cloud images, since in that
case cloud-init takes care of resizing the root filesystem and
the underlying partition together with all the other setup
tasks.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
We only really need i686/x86_64 libraries, and executables which do not exist
(or do not work equivalently) on the arm64 host system.
In particular, removing libexec avoids situations where random dbus services
are started under emulation for no reason.
We're currently shipping GTK2/3 libs in the rootfs. While we're doing
that, let's also install XIM support, which actually works through X11
passthrough with muvm. This should generally make legacy GTK x86_64
apps have input method support the old-fashioned way.
Modern apps should use the Wayland input method protocol stuff, which is
already built into GTK3/GTK4 and should not require any extra shared
libraries for FEX. For muvm, that will work once we have Wayland
passthrough.
Per #112, excluding group specs just does not work in Kiwi at
present. For LXQt this is especially a problem because it means
the image fails to compose. The exclusion of m17n* *does* work
as it's a package spec, but because the exclusion of the
input-methods group does not work, dnf wants to install
ibus-typing-booster (part of input-methods), which requires
m17n-lib, and these conflicting requirements cause it to blow up.
So at least until the problem of not being able to exclude
groups is resolved, we should drop these.
Arguably, we should permanently stop excluding input-methods, at
least. Space constraints aren't as huge of a deal these days as
they used to be, on the whole; lots of folks have decent bandwidth,
lots of disk space, and large USB sticks. Input methods are
critical for CJK users; leaving them off the image makes it more or
less useless for them, which is a significant impairment. (Unless,
that is, input methods don't work properly in LXQt even if included
- I haven't tested this).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Many of the older supported AArch64 systems (particularly single
board computers) require a legacy MBR (Master Boot Record) type
partitioning to successfully boot.
Many of the older supported AArch64 systems (particularly single
board computers) require a legacy MBR (Master Boot Record) type
partitioning to successfully boot.
Group exclusions do not seem to work anymore with DNF5, so explicitly
filter out unwanted packages. Additionally, add missing unwanted
packages from the kickstarts and refactor it to apply to both
KDE Desktop and KDE Mobile profiles.
As it currently stands, this doubles the size of the live ISOs,
which is completely unacceptable.
We will need to make the switch eventually, but we need to figure
out how to compress better first.
This reverts commit 1457e97008f15064dcc30aaca9977ffa1ec66572.
