asahi-fedora-usb VS mkosi

you're gonna have to build this on an x86 pc. sudo dnf install arch-install-scripts bubblewrap gdisk qemu-user-static rsync systemd-container python3 -m pip install --user git+https://github.com/systemd/mkosi.git git clone https://github.com/leifliddy/asahi-fedora-usb.git cd asahi-fedora-usb

Once you install Asahi Linux (or just the bootloader) you could simply boot a usb drive https://github.com/leifliddy/asahi-fedora-usb via u-boot and easily mount + access any unencrypted internal Linux partitions.

However, if you already have asahi linux installed, you can use this project to create a bootable external drive: https://github.com/leifliddy/asahi-fedora-usb

On Arch Linux ARM with Asahi, I tried getting virtualisation to work as well. However, two other essential things you need is edk2 and qemu. However, both of those are not truly available in Arch Linux ARM. So I tried building qemu from source, which worked. But setting edk2 up was just a nightmare for my short attention span. I snooped around online and found that both Fedora and Ubuntu have pretty good support for virtualisation in aarch64. I found some .deb packages online which could satisfy edk2 and qemu for libvirt. Using debtap from the AUR, you could convert these packages and install them on ALARM. Or, you could use an installation of Debian on Fedora on your Mac to just install the packages directly to get virt-manager working perfectly. Since I love ALARM on my Mac, but still want Fedora for virtualisation, I've been trying to use this project by @leifliddy that lets you boot Fedora in a USB on top of your Asahi Linux installation (as long as you have u-boot). This is bloated with empty words, so if you want some thorough guide, I can document it for you.

I work with a free and open-source software community called Fedora Project. I had the opportunity to moderate the talk of one of the maintainers of the Systemd suite during the annual contributor conference, Flock To Fedora 2023 where he talked about a tool named Mkosi.

For testing i prefer systemd-nspawn containers with mkosi. A neat tool for running your other fav. distro in a terminal. Works like a charm and integrates nicely in your system. Eg. logs and systemd services or CI testing.

- https://github.com/systemd/mkosi

- man:systemd-nspawn(1)

- man:machinectl(1)

you're gonna have to build this on an x86 pc. sudo dnf install arch-install-scripts bubblewrap gdisk qemu-user-static rsync systemd-container python3 -m pip install --user git+https://github.com/systemd/mkosi.git git clone https://github.com/leifliddy/asahi-fedora-usb.git cd asahi-fedora-usb

There's also mkosi: https://github.com/systemd/mkosi. This one outputs an iso or similar image file and supports many base distributions.

[1] https://github.com/systemd/mkosi/issues/376

System's mkosi is worth checking out too: https://github.com/systemd/mkosi I don't think it generates docker/OCI images directly, but it definitely can generate a tarball of the final image contents and then crane of a similar tool could package it up into an appropriate image. For just docker usage it's probably overkill, the main advantage would be it can build other image types like adding a kernel and init to be a fully bootable iso of VM image.

Constellation ensures that all K8s nodes run on AMD-based Confidential VMs (CVMs). CVMs are strongly isolated from the host and remain encrypted in memory at runtime. Constellation also ensures that all nodes run the same minimal mkosi-based node image.

At first glance I thought your project is a frontend for mkosi but then I saw that you support non-systemd targets too. Mentioning it here because it may be relevant to other users/developers.