This is how Linux fragments, and ultimately dies as the Linux we know. I'm not really making a value judgement, just an observation.
CoreOS is building a container runtime, Rocket
51–60 of 295 posts
Re: CoreOS is building a container runtime, Rocket
#52I have been concerned that Docker's scope was expanding too far for a while now, so I'm glad to see an alternative that might work appear on the horizon. That said, I am somewhat concerned that CoreOS has a suspiciously similar business model to where Docker would probably like to be. It's in a business's best interest, and exceedingly common practice, to "land and expand" with something clear and compelling, and fol…
Re: CoreOS is building a container runtime, Rocket
#53Earlier quoted context omitted.
This is exactly the model being proposed in Docker.
I think this was the original model proposed by Docker. What we have now is (as other posters have mentioned), a Docker organization reasonably bent towards creating value for their investors, which means they need to start building things that, you know, make money. To clarify, I don't think there's anything inherently wrong with what Docker's doing, but it is at odds with an entirely open, pluggable system. It does…
Re: CoreOS is building a container runtime, Rocket
#54I'm looking into using containers for ui applications. I need to access GPU within the application. is this doable with Rocket or Docker?
Also does Rocket have to be used with CoreOS?
Re: CoreOS is building a container runtime, Rocket
#55Re: CoreOS is building a container runtime, Rocket
#56Rocket is tied to systemd, that will definitely spawn some interesting discussions. https://github.com/coreos/rocket/blob/9b79880d915f63e7389108...
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.
One thing that I believe Docker has failed at is in taking a purely declarative approach to image definition; rather than specifying the packages that are assembled/inserted to create the container, Docker ships around non-portable Linux binaries.
Re: CoreOS is building a container runtime, Rocket
#57http://blog.docker.com/2014/12/initial-thoughts-on-the-rocke...
Re: CoreOS is building a container runtime, Rocket
#58This may be a noob question, I'm looking into using containers for ui applications. I need to access GPU within the application. is this doable with Rocket or Docker? Also does Rocket have to be used with CoreOS?
Re: CoreOS is building a container runtime, Rocket
#59Rocket is tied to systemd, that will definitely spawn some interesting discussions. https://github.com/coreos/rocket/blob/9b79880d915f63e7389108...
The great part of having a spec separate from the runtime is that Rocket can use systemd, but other compatible tools won't have to.
Re: CoreOS is building a container runtime, Rocket
#60I have been concerned that Docker's scope was expanding too far for a while now, so I'm glad to see an alternative that might work appear on the horizon. That said, I am somewhat concerned that CoreOS has a suspiciously similar business model to where Docker would probably like to be. It's in a business's best interest, and exceedingly common practice, to "land and expand" with something clear and compelling, and fol…