mkosi

I'll give this one a try, thanks for sharing! FWIW, I'm currently using systemd-nspawn via mkosi: https://github.com/systemd/mkosi It makes an image and runs it in separate namespace. It can start at bash or init. It's very fast but there seem to be a problem creating an Ubuntu image on Debian and vice versa.

I use mkosi: https://github.com/systemd/mkosi Which is just a front for systemd-nspawn. It's annoying you have to edit the config.nspawn to mount a directory if you start it with the "shell" command, instead of booting. But apart from that, it's brilliant.

Excellent super slept on distro using excellent super slept on distro assembly tools also homed in the systemd cinematic universe, mkosi, https://github.com/systemd/mkosi

For Linux this will vary between distributions and configurations. For example, based on some testing I did today using mkosi [1] (for reasons unrelated to this discussion), a bare-bones Fedora 43 installation uses about 130 MiB of RAM, while a Debian installation uses a little more than 100 MiB. IIRC last time I tried a bare-bones FreeBSD installation it used about the same amount of memory, maybe a little more based on how ZFS is set up. [1]: https://github.com/systemd/mkosi

Does seem to support cross-architecture image building, which is a feature that's kept me on Debian's multistrap and now mmdebstrap. I should give this a go! The README's reference page has some good write-ups et cetera! There's a good "re-introduction" on Lennart (creator of systemd, mkosi) site, from the current maintainer. https://github.com/systemd/mkosi?tab=readme-ov-file#referenc... https://0pointer.net/blog/a-re-introduction-to-mkosi-a-tool-...

The alternative is mkosi from systemd developers https://github.com/systemd/mkosi However beware that they break backwards compatibility almost every 6 months. This is probably the most backwards-incompable project I know, you can't rely that the minor version update won't break your projects.

If you're implying something, then please get your thoughts across more clearly. The title says "profit goes to open-source", meaning CUPS, SANE, AirSane projects, which are FOSS (free and open-source), if the publicly available code and collaborative development is what you're referring to. Additional software (web interface, scripts, utilities) is free, the source code is included in the source package. The customer is provided with the source code of the firmware components, and with the build system based on mkosi[1] to build the complete firmware: starting from bootstrapping Debian 12 builder image which cross-compiles the packages with additional patches and builds additional software, to ARM Debian 12 image with everything compiled in the previous stage, to the final squashfs OS file and MicroSD image. [1]: https://github.com/syste

There's lots of tools in this space. I work on https://github.com/systemd/mkosi for example.

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)

Systemd'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 filesystem image contents and then crane or a similar tool could package it up into an appropriate OCI 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 or VM image, in addition to just getting a container image.