2 ms·
I'm not super familiar with either, but as I understand it, systemd-nspawn is only an alternative to "docker run". The docker command supports all sorts of othe
by geofft 12y ago
I'm not super familiar with either, but as I understand it, systemd-nspawn is only an alternative to "docker run". The docker command supports all sorts of other things, like creating container images, manipulating, uploading, etc. systemd-nspawn just runs things, and the upstream docs suggest using debootstrap, yum, etc. to create a thing for nspawn to run. (Running things is both the easy part, and the part that most makes sense for an initsystem / system daemon to do.)
systemd-import will grab Docker images from the internet, but I'm not sure it will do very much else. In other words, even if you adopt systemd's way of doing things in deployment, your developers are still using the docker command.
- justincormack 12y agoWell thats kind of why Rocket from CoreOS is writing specs and splitting these things up [1] so you can use different tooling. [1] https://github.com/appc/spec/blob/master/SPEC.md https://github.com/appc/spec/blob/master/SPEC.md