#mkosi — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mkosi, aggregated by home.social.
-
Documentation on how to build #mkosi images, with all the #systemd security-relevant goodies, on SUSE's OBS @obshq is now published: https://openbuildservice.org/help/manuals/obs-user-guide/cha-obs-package-formats#sec-pkgfmt-mkosi
(NB: until we tag the next release this requires mkosi built from git main, hint hint @daandemeyer )
-
🔥 Image-based Linux with systemd [EN]
@zbyszek, a #systemd developer and #Fedora maintainer, will explore the future of image-based, immutable, cryptographically verified #Linux installations, covering engineering challenges, secure updating/extending, and how tools like #mkosi build installation images, initrds, and extensions from distro packages.
📍 Where: Hotel przy Młynie, Rybnik
📅 When: 24–26 October 2025
🔗 Register now: https://jesien.org/2025/zapisy -
I wrote a blog post around modern secure boot options for embedded Linux devices. It showcases how new systemd features provide a turn-key solution for problems that previously required a lot of custom integration.
-
Mkosi – Build Bespoke OS Images
#HackerNews #Mkosi #BespokeOS #CustomImages #LinuxDevelopment #Systemd
-
Mkosi – Build Bespoke OS Images
#HackerNews #Mkosi #BespokeOS #CustomImages #LinuxDevelopment #Systemd
-
Mkosi – Build Bespoke OS Images
#HackerNews #Mkosi #BespokeOS #CustomImages #LinuxDevelopment #Systemd
-
Mkosi – Build Bespoke OS Images
#HackerNews #Mkosi #BespokeOS #CustomImages #LinuxDevelopment #Systemd
-
Mkosi – Build Bespoke OS Images
#HackerNews #Mkosi #BespokeOS #CustomImages #LinuxDevelopment #Systemd
-
Introducing initial support for #postmarketOS in #mkosi 🥳
-
Found some examples in this repo:
https://github.com/nosada/mkosi-files
Have several build attempts, but still struggle at customizing the built image automatically: file access permissions aren't allowing modifications, sudo in the container does not work, etc.
Anyways, liking that mkosi / systemd-nspawn nicely integrate into the systemd ecosystem - and come with superb documentation.
-
@katzenmann @chimera_linux yeah once we get mount namespaces going as well and some more pluggable CLI i will absolutely be dropping a justfile in and composing more complicated setups like having packages to build firmware.
we could also then pretty easily add some #mkosi templates to wrap pmb so you can easily script building custom images.
-
What I did yesterday:
- I was trying to get a new version of the nspawn-fuse PR ready
- but I went down some yaks with the #systemd tests, ending up with some hacking on #mkosi.What I'm doing today:
- A little more work on mkosi. I want better reporting of its capabilities based on what's installed; no more "error, do you have createrepo_c installed?" 20min into a build. I want a real #Parabola story for mkosi.
- Anyway, I'm too many yaks deep, I should get back to nspawn-fuse. -
So it turns out the #systemd integration tests skip anything that requires HAVE_VMLINUX_H, because
(1) it is of course good that the tests skip this and proceed on platforms that won't have it
(2) the integration tests use systemd as-built-by `mkosi.build.chroot`, and #mkosi uses bwrap for .chroot scripts, and bwrap doesn't mount /sys, and generating vmlinux.h depends on /sys/kernel/btf/vmlinux existing, so HAVE_VMLINUX_H will never be true for the nsresourced used in the integration tests. -
@NeunMalKlug you can use them to e.g. build virtual machine images for other distributions using #mkosi.
-
My hyperfixation the past few months has been working on an image based system, mostly inspired by @pid_eins "Fitting Everything Together" Blog.
While I find most of it really good, I did have some thoughts about the partition layout that was proposed and I wrote them down in a gist https://gist.github.com/NekkoDroid/f5ecc9540863eaad7752f73587b419de
The issues are around dual-booting, having more locations writable then needed and splitting /home/ to a separate partition.
-
From #CentOSConnect: Daan De Meyer showed how to test the CentOS Hyperscale systemd backport with mkosi.
-
From #CentOSConnect: Akashdeep Dhar showed how to build operating system images using mkosi.
-
Use mkosi to build distribution images! This article walks through RHEL and RHEL UBI as examples, but Debian, Ubuntu, Arch, openSUSE, and more are also supported for building. ⚙️
➡️ https://fedoramagazine.org/create-images-directly-from-rhel-and-rhel-ubi-package-using-mkosi/
-
@arichtman even more sorcery, when it's paired with #mkosi and #machinectl!
Like "why the hell did I ever sell my soul to hack together VM-based and hard to reproduce testing environments?"
But since @nobodyinperson is mostly on #NixOS anyways, all this doesn't really matter, thanks to "nixos-rebuild build-vm" 😁
-
https://kilabit.info/journal/2023/using_systemd_mkosi_2/
Using #systemd #mkosi for development, round 2.
Previously, we try hard to make the "mkosi.build" script test our awwan application, because we want a simple flow. Unfortunately, it does not work.
In this attempt, I would like to take different approach. Instead of building and running the container in single "make", we booted up the container first and then trigger running the test from host using command "machinectl awwan@image …".
-
Using #systemd #mkosi for development [1].
In this journal, I will take a notes on my journey learning and using mkosi as part of integration tests for developing awwan [2]. The goal is that when I run make on awwan repository, it will create and run a container using systemd-nspawn(1) with SSH server running, and run all tests inside the container.
[1] https://kilabit.info/journal/2023/using_systemd_mkosi/
[2] https://sr.ht/~shulhan/awwan -
-
@lcruggeri in this case it is #ArchLinux
I'm currently building a test setup for an update scenario for A/B boot and ran into this weirdness. (so luckily at least all VM weirdness)
FWIW, I'm building an image using #mkosi and then build my own A/B image using the separate artifacts.
-
Is anyone using #mkosi (from #systemd) to build images for their desktop machines? I wanted for my new hardware to be #immutable from the start, but am struggling with finding a workflow that would allow me to do updates with not too much manual effort (i.e. A/B updates are probably a must).
-
