News for hackers. Stuff that matters.
Re:Systemd can now pull and update container images from the... by vruiz on Saturday January 17, 2015 @10:50AM (#8904528)
It's not about docker, it about systemd-nspawn which is systemd's own alternative to docker.

I'm with you here, at first I didn't understand the alarm but now I'm starting to see the danger of this trend.

Re:Systemd can now pull and update container images from the... by ris on Saturday January 17, 2015 @11:36AM (#8904674)
I don't think systemd is moving into this territory just for fun. I seem to recall it's because now the kernel is moving towards unified cgroups-trees if systemd wants to be able to use cgroups it more or less has to be "in charge" of them at the root, meaning it's going to have to take care of this sort of functionality.
Re:Systemd can now pull and update container images from the... by digi_owl on Saturday January 17, 2015 @02:10PM (#8905197)
Last i read on LWN the cgroups kernel dev was backing away from the idea of having a singular cgroups management daemon.

And no, its not just for fun. RH is betting big on competing with Amazon and MS on cloud services. It would not surprise me if they are trying to get old RHEL server customers to move their servers onto the RH cloud with the switch to RHEL7.

Re:Systemd can now pull and update container images from the... by sciurus on Saturday January 17, 2015 @11:47PM (#8906667)
What Red Hat cloud?
Re:Systemd can now pull and update container images from the... by digi_owl on Sunday January 18, 2015 @05:32AM (#8907190)
Re:Systemd can now pull and update container images from the... by sciurus on Sunday January 18, 2015 @09:04PM (#8909910)
That doesn't answer the question. To clarify, what I meant was that Red Hat doesn't run a public IaaS cloud to which people can "move their servers".
Re:Systemd can now pull and update container images from the... by jacquesm on Saturday January 17, 2015 @11:38AM (#8904682)
Linux should simply adopt jails and get it over with rather than to get stuck in NIH territory.
Re:Systemd can now pull and update container images from the... by ris on Saturday January 17, 2015 @11:50AM (#8904715)
Right. They should "port" a feature that's intricately linked with the internal workings of a kernel over from another completely alien kernel.
Re:Systemd can now pull and update container images from the... by jacquesm on Saturday January 17, 2015 @11:52AM (#8904726)
Nobody said it would be easy.
Re:Systemd can now pull and update container images from the... by ris on Saturday January 17, 2015 @02:08PM (#8905191)
You... more or less implied it
Re:Systemd can now pull and update container images from the... by dezgeg on Saturday January 17, 2015 @12:33PM (#8904852)
Cgroups are not a virtualization / containerization feature like jails, their use cases are entirely different.
Re:Systemd can now pull and update container images from the... by geofft on Saturday January 17, 2015 @11:45AM (#8904700)
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.

Re:Systemd can now pull and update container images from the... by justincormack on Saturday January 17, 2015 @11:51AM (#8904724)
Well 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