Nspawn 3.0: A Docker-compatible Engine API for systemd-nspawn containers
20 points by diktomat
20 points by diktomat
Ohh! Amazing, I'll definitively give this a shot. I'm building docker images with nix2container and was working on .mstack compatibility - so I can benefit from nix layering.
This kinda fit's really well into some other systemd-nspawn endeavors I was looking into, single big VM/computer running systemd-nspawn containers - but I also just want to run docker as well for some services, so this fits perfectly into that gap.
Really much looking forward into the future compatibility of nested systemd-nspawn, this would give the entire setup an even higher value.
I think what I'm going to investigate next is how skoepo and mstack can be combined - any ideas on that front? Issue was closed as not planned, but some pointer was left behind.
It answers in the shapes of API 1.51, and of the versions down to 1.24 that clients ask for.
The article starting in a really weird way (as if the introduction is missing) was suspicious, but this makes it pretty clear this wasn't written by a human; or at least a very lazy one.
Makes it incredibly hard to read, because why should I care at all? If it's worth releasing it's worth writing a couple sentences about each feature surely
That's exciting. I was a fan of the rkt idea and this goes in the same direction - we already have a process supervisor aware of namespaces. When trying to write my own version of that I ran into lots of issues with systemd's import just not supporting lots of cases for OCI and gave up. I'm glad they had a similar idea and succeeded.