Comment by Ferret7446
1 day ago
How so? nspawn means spawn a process in a new namespace, which is... exactly what it does. The problem isn't with systemd-nspawn, the problem is with containers, because the vast majority of devs have no idea that containers are just scripts to set up Linux namespaces.
> because the vast majority of devs have no idea that containers are just scripts to set up Linux namespaces.
That’s IMO framing things a bit backwards.
That’s how containers are implemented… today. on Linux. On Windows it’s completely different. On MacOS it’s completely different again.
And what makes you think «namespaces» are a term unique to containers? It’s used throughout tech for a million other platforms too.
Containers however is a well defined concept, regardless of how they are implemented today, and on one platform only.
systemd would probably see more use of their container-platform if they put «container» in the name, that much seems obvious to me.