Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CoreOS is building a container runtime, Rocket

coreos.com

Post reply on HN
Print view View original

101–110 of 295 posts

Re: CoreOS is building a container runtime, Rocket

#101

Post by pnathan »

superuser2 wrote: post #74
tveita wrote: post #47

Earlier quoted context omitted.

What is Docker's 'new' direction? I don't see any related announcements on their blog besides adding support on new platforms.

Docker's 'new' direction is to direct its attention towards solving the orchestration and management problems involved in actually running infrastructure on Docker. A number of third parties had begun work on various (sometimes proprietary) orchestration and management systems for creating a reliable/scalable/easily manageable cluster with Docker as a building block. CoreOS is one. But Docker is pushing towards an of…

> Docker's 'new' direction is to direct its attention towards solving the orchestration and management problems involved in actually running infrastructure on Docker.

IME examining Docker, this is actually the hard problem.

Re: CoreOS is building a container runtime, Rocket

#102

Post by xorcist »

shykes wrote: post #87

Hi, I created Docker. I have exactly 3 things to say: 1) Competition is always good. Lxc brought competition to openvz and vserver. Docker brought competition to lxc. And now tools like lxd, rocket and nspawn are bringing competition to Docker. In response Docker is forced to up its game and earn its right to be the dominant tool. This is a good thing. 2) "disappointed" doesn't even begin to describe how I feel about…

What's with all the drama? Did we read the same announcement?

What is it that we end users don't know?

Re: CoreOS is building a container runtime, Rocket

#103

Post by rdtsc »

shykes wrote: post #87

Hi, I created Docker. I have exactly 3 things to say: 1) Competition is always good. Lxc brought competition to openvz and vserver. Docker brought competition to lxc. And now tools like lxd, rocket and nspawn are bringing competition to Docker. In response Docker is forced to up its game and earn its right to be the dominant tool. This is a good thing. 2) "disappointed" doesn't even begin to describe how I feel about…

> Hi, I created Docker. I have exactly 3 things to say:

In line of making lists of things to say. I got 2.

1) Don't use Twitter for having long conversations and public fights. Just don't. No good will come out of it. Engaging in that is feeding the trolls and slinging mud, which you accuse the other party of doing.

2) Vis-a-vis "just compete!". How do you see this "competing" happening without an announcement like this. "We have created X container thingy"? Ok, isn't it smart to compare to an existing container "thingy" right of the bat?

Imagine they didn't mention Docker. I can see you writing about "stealing of ideas", "lies", "not being straight-forward", "this is just a Docker clone by they don't mention Docker so they are being shady" and so on.

Re: CoreOS is building a container runtime, Rocket

#105

Post by lclarkmichalek »

[deleted] wrote: post #100
spb wrote: post #92

Earlier quoted context omitted.

I think you're reading too much - or too little - into this if you think they're "slinging mud". Any fork is going to list its reasons for the fork- if they didn't have issues with how Docker is heading, why would they be making the fork in the first place? If they just quietly gave an ambiguous non-disparaging statement like "we're forking because we're unhappy with the direction Docker is taking", it would seem fri…

[deleted]

Might be worth mentioning that you are employed by Docker, if you're going to engage in this discussion.

Re: CoreOS is building a container runtime, Rocket

#107

Post by billconan »

pron wrote: post #58
billconan wrote: post #54

This 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?

I'm interested: why do you need a container for a UI application? It would be better for your users if it could run as a simple process.

I actually need gpu, not the ui. I need it to do scientific computation. Video streaming service is another case. gpu has better video encoding capabilities.

I previously heard that docker has trouble loading device drivers.

Re: CoreOS is building a container runtime, Rocket

#108

Post by billconan »

wmf wrote: post #70
billconan wrote: post #54

This 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?

GNOME is working on sandboxing + application packaging that's basically containers under a different name. http://blogs.gnome.org/aday/2014/07/10/sandboxed-application... http://blogs.gnome.org/uraeus/2014/07/10/desktop-containers-... http://www.superlectures.com/guadec2013/sandboxed-applicatio...

thank you very much. I will take a look. but the fact that this is tied to Gnome worries me. I actually need a console application with gpu access.

Re: CoreOS is building a container runtime, Rocket

#109

Post by billconan »

bgwhn wrote: post #69
billconan wrote: post #54

This 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?

Certainly. The kernel can simply pass through the device, although you lose some of the security of containerization that way. There may be issues with multiple containers sharing the same GPU though.

I indeed need multiple containers to share the same gpu. :(

Re: CoreOS is building a container runtime, Rocket

#110

Post by shykes »

rdtsc wrote: post #103
shykes wrote: post #87

Hi, I created Docker. I have exactly 3 things to say: 1) Competition is always good. Lxc brought competition to openvz and vserver. Docker brought competition to lxc. And now tools like lxd, rocket and nspawn are bringing competition to Docker. In response Docker is forced to up its game and earn its right to be the dominant tool. This is a good thing. 2) "disappointed" doesn't even begin to describe how I feel about…

> Hi, I created Docker. I have exactly 3 things to say: In line of making lists of things to say. I got 2. 1) Don't use Twitter for having long conversations and public fights. Just don't. No good will come out of it. Engaging in that is feeding the trolls and slinging mud, which you accuse the other party of doing. 2) Vis-a-vis "just compete!". How do you see this "competing" happening without an announcement like t…

> 1) Don't use Twitter for having long conversations and public fights. Just don't. No good will come out of it.

I encourage you to read the twitter exchange I linked to. It predates all of this, and is not at all a fight. On the contrary it is a constructive exchange and I am using it to assert Docker's philosophy in a positive way

> Vis-a-vis "just compete!". How do you see this "competing" happening without an announcement like this. "We have created X container thingy"? Ok, isn't it smart to compare to an existing container "thingy" right of the bat?

Surely it's possible to launch a competing tool without resorting to a press campaign like this one: http://techcrunch.com/2014/12/01/coreos-calls-docker-fundame...

> Imagine they didn't mention Docker. I can see you writing about "stealing of ideas", "lies", "not being straight-forward", "this is just a Docker clone by they don't mention Docker so they are being shady" and so on.

No, I would definitely not say that.

Post reply on HN