News for hackers. Stuff that matters.
Re:How is Docker.io different from a normal virtual machine? by darklajid on Friday September 13, 2013 @05:23AM (#6379383)
Regarding your first footnote:

Is there an explanation why 'in production' is actively discouraged? Is that a limitation of the underlying lxc stuff?

I ask, because the interesting parts of docker _for me_ seem to be focused on the setup, deployment - and not the runtime. So if I create a working image and want to use that in production, wouldn't docker become passive as soon as I run that thing?

What's the danger here?

Re:How is Docker.io different from a normal virtual machine? by pekk on Friday September 13, 2013 @12:08PM (#6381348)
I expect the danger is that someone will lose money and blame the developers for as-yet unforeseen issues which can only be smoked out after a few years of heavy use. But a specific danger would be interesting to hear.
Re:How is Docker.io different from a normal virtual machine? by shykes on Friday September 13, 2013 @02:12PM (#6382085)
Docker maintainer here. That's basically it. There's no specific danger that we're worried about - just engineering best practices.

As long as we're not comfortable operating Docker at large scale ourselves (we run quite a lot of containers in production at dotCloud), we won't recommend that others do it.