jamtur01

8 ms·

31.
by jamtur01 13y ago
The first step there is boot2docker - http://boot2docker.io/ - for OSX and Windows. I don't think Docker 1.0 will have native server support for either operating system but I'd be very surprised if it wasn't
32.
by jamtur01 13y ago
Hi We didn't have an irresponsible disclosure. We did recently present some of this information and were asked about our security policy. That policy wasn't yet published or announced so we decided it was important to get it out t
33.
by jamtur01 13y ago
Oops. Looks like a little hiccup but we're back.
34.
by jamtur01 13y ago
Docker does not (yet) support 32-bit architectures.
35.
by jamtur01 13y ago
Not if it's an option for installation. Or if they start shipping them like that. Steam springs to mind. :)
36.
by jamtur01 13y ago
Try here: http://www.docker.io/learn_more/
37.
by jamtur01 13y ago
We building a more pluggable Docker for 1.0. The execution engine and a bunch of the components will be pluggable via API. You can then pop in an execution engine that runs on Windows and get the benefits of Docker.
38.
by jamtur01 13y ago
I did exactly that with Puppet as an experiment: http://kartar.net/2013/12/building-puppet-apps-inside-docker... . Works reasonably well. I will say though that the Dockerfile syntax is, IMHO, much easier to use th
39.
by jamtur01 13y ago
There's also Boot2Docker which I've been using on OSX - https://github.com/steeve/boot2docker .
40.
by jamtur01 13y ago
And there's boot2docker for OSX that's even more lightweight than Vagrant - https://github.com/steeve/boot2docker .
41.
by jamtur01 13y ago
We will be providing commercial support for open source Docker this year. If you're interested please email me at james@docker.com.
42.
by jamtur01 13y ago
The blog post on our site explains what comes next: http://blog.docker.io/2014/01/docker-closes-15-m-series-b-fu... Quoting from that: "While Docker itself will always remain free and open source, we are busy
43.
by jamtur01 13y ago
This blog post on the road to Docker 1.0 will also give you an idea of what we have planned albeit the timelines might be a little different: http://blog.docker.io/2013/08/getting-to-docker-1-0/ .
44.
by jamtur01 13y ago
Woot! Very excited! :)
45.
by jamtur01 13y ago
That's just by default though. You can easily run upstart (or other init styles) inside Docker. Additionally you can use a number of base images if the stock Ubuntu image doesn't suit you.
46.
by jamtur01 13y ago
It's fairly easy to integrate configuration management tools into your Docker workflow - I wrote a blog post about it here: http://kartar.net/2013/12/building-puppet-apps-inside-docker... .
47.
by jamtur01 13y ago
That's awesome to hear! If you have any feedback on the documentation or would like to see other material please reach out to me: james.turnbull@docker.com. Or log a ticket and cc me on GitHub: jamtur01.
48.
by jamtur01 13y ago
I think they can co-exist: the market and the use cases are really broad and there's a lot of space for a wide variety of tooling. I wrote a blog post about Docker and Configuration Management that elaborates on this: http:/&#x2F
49.
Building Puppet-based applications inside Docker(kartar.net)
1 points by jamtur01 13y ago|0 comments
50.
by jamtur01 13y ago
Politely it's not bollocks but perhaps I should have used better wording and replaced "process" with "service". :) I look at Docker as a lightweight way of modeling infrastructure and services. I can built a shiploa
51.
by jamtur01 13y ago
It's flying cars isn't it? Please tell me it's flying cars.
52.
by jamtur01 13y ago
This slide deck has a pretty good explanation of the solution: http://www.slideshare.net/dotCloud/why-docker2bisv4
53.
by jamtur01 13y ago
You can do both. Docker containers by default are designed to run a single process but you can use a process manager like supervisord or a script to run many too.
54.
by jamtur01 13y ago
Neat idea. What's the underlying technology creating the QA environment? A virtual machine? A container? How is it being configured? A CM tool?
55.
by jamtur01 13y ago
He was the product manager some years ago and very briefly.
56.
by jamtur01 13y ago
Neat! Great to have an ecosystem of content starting to grow. The Creative Commons license chooser is a good way to go: http://creativecommons.org/choose/ . And their "before licensing" page is pretty good too
57.
by jamtur01 13y ago
I write mostly in Markdown using VIM or IAWriter with a scattering of LaTeX for some complex formatting. I have some Rake-based automation that hooks into pandoc to take the content and generate PDF, ePub, Mobi, HTML etc formats. You can s
58.
by jamtur01 13y ago
Hi - I'm the author. It is very early. But the book won't be published until Docker is 1.0 at least. The site is there to gauge interest and provide a bookmark for people to suggest ideas on content.
59.
by jamtur01 16y ago
You're missing my point - it's a RubyGems issue not a Debian one. Standards matter.
60.
by jamtur01 16y ago
Don't package them isn't a solution. It's sticking your head in the sand. Again and again in the Ruby world I see the "it works for us web developers on the x number of hosts we run". The people who use Ruby for stand-alone applications ac

More ›