Kai Lüke

I see https://github.com/pi-pi3/ext2-rs which could be a starting point but not sure how usable it is for this purpose

I would recommend to look at https://github.com/kata-containers/kata-containers - basically you would only have replace the Linux kernel when setting it up :crossed_fingers:

> This is already the case, only the ID field is mandatory. That's only for the `isempty(host_os_release_version_id)` case where a rolling release host like ArchLinux has no `VERSION` set. >...

> We don't check the distro name, as we really don't want to maintain that list. We have tests in place enforcing that just having `ID` and nothing else works...

Yes, or semver comparisons like for dependencies in Cargo.toml would be even better but that's for later ;) For the case of having `ID=any` the version field doesn't make sense...

Didn't make it this week but probably the 2nd week of August should work

PR posted, I've also used the `any` value in the `ARCH` field to distinguish between an extension with an unkown/unspecified architecture and an extension that is arch-independent. I think it...

You can build arm64 images as follows on your current x86 Linux environment: Install the `qemu-user-static` package for your system which should include `qemu-aarch64`. Then maybe do a `sudo systemctl...

We could set it up in parallel and eventually migrate the domain when needed: https://gohugo.io/hosting-and-deployment/hosting-on-github/#branches-for-github-actions

Found a gitlab MR that also added support for the same format: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78934/diffs At first it's a bit confusing that `-sk` suffix of the format name becomes a prefix in...