really marked of your discussion to me ,a white to what is UNIX philosophy ,either the dockers !Guys from China longing for theway of LINUX or UNIX culture!
CoreOS is building a container runtime, Rocket
291–295 of 295 posts
Re: CoreOS is building a container runtime, Rocket
#292really marked of your discussion to me ,a white to what is UNIX philosophy ,either the dockers !Guys from China longing for theway of LINUX or UNIX culture!
Re: CoreOS is building a container runtime, Rocket
#293Docker just posted a blog response http://blog.docker.com/2014/12/initial-thoughts-on-the-rocke...
Thanks, Docker team, this made me 100% sure I support Rocket.
Re: CoreOS is building a container runtime, Rocket
#294Earlier quoted context omitted.
It isn't tied to systemd. The stage1 that is in the current prototype uses systemd to monitor and fork processes but we would love to see other stage1's that configure other process runners. For example configure and run a qemu-kvm filesystem as the container. Also, even though it is using systemd to monitor and fork processes a design goal is to run on all Linux's that have a modern Kernel.
The app container specification has socket activation in it. This is going to essentially tie it to systemd. Otherwise you will need another daemon running to do the socket activation, but then that would seem to be a "fundamentally flawed" execution model.
Socket activation does not need systemd in any way. You can launch any socket-activated daemon with https://github.com/LEW21/sdlaunch - without any dependence on systemd.
Re: CoreOS is building a container runtime, Rocket
#295Earlier quoted context omitted.
> Even stupidest things like allowing to have more dockerfiles in one folder. Wow. That issue has been open for a long time.
I've been involved in that ticket since the dark ages. There's a philosophical disconnect between how (some) people want to use Docker and how the maintainers want it to be used, and it comes to a head in that thread.
For anyone else trying to follow along (and still evaluating docker at a distance), start with this comment in that thread:
https://github.com/docker/docker/issues/2112#issuecomment-39...
It gets quite interesting, and it's still going 14 months later...