Live data from Hacker News

Docker interactive tutorial

blog.docker.io

11–20 of 48 posts

Re: Docker interactive tutorial

#14
post #8

I never understood what docker is or who is supposed to use it. Can somebody enlighten me?

Regarding who is supposed to use it... If you like deploying your apps to a Platform-as-a-Service (PaaS) like Heroku, Google AppEngine, or DotCloud, but wanted to run it on your own infrastructure, then Docker could be for you!

It's designed to be a key building block for anyone who wants to create their own PaaS-like service or environment. Why would you need your own PaaS? You might have unique security requirements forcing you to run an app in-house, or you might not want to pay the high prices of a commercial PaaS if your app gets popular.

Re: Docker interactive tutorial

#15
post #9
post #8

I never understood what docker is or who is supposed to use it. Can somebody enlighten me?

It depends. Do you mind me asking, what is your background/profession? And have you deployed a virtual machine before to run an application?

Im a coder and owner of a small SaaS company.

What I do to run applications is this: I fire up a vm or dedicated server on some provider and run my stuff on it. I use Amazon and a couple of other providers.

Re: Docker interactive tutorial

#16
post #14
post #8

I never understood what docker is or who is supposed to use it. Can somebody enlighten me?

Regarding who is supposed to use it... If you like deploying your apps to a Platform-as-a-Service (PaaS) like Heroku, Google AppEngine, or DotCloud, but wanted to run it on your own infrastructure, then Docker could be for you! It's designed to be a key building block for anyone who wants to create their own PaaS-like service or environment. Why would you need your own PaaS? You might have unique security requirement…

So I'm used to configuring stuff by hand, and now I see a lot of buzz around docker, vagrant, chef, puppet, salt and they seem like glorified shell scripts. Am I missing something?

Re: Docker interactive tutorial

#17
post #2

The creator here. Please let me know if you have any questions or comments!

Hi dhrp, I assume you work for Dotcloud? Nice job so far. Where do you see this heading to? What's your view of what will happen in the virtualization world? Best,

Hi. Thanks! My personal take on where Docker is heading to? There are so many things people can do with this, it's hard to summarize.

What I personally care most about? As a designer ex-entrepreneur and front-end developer, the thing that gets me going most is the idea that I'm able to "just run" an application. No more difficult than from the Mac store. For example Trac (a wiki system), Wordpress, Django apps, Mailservers, torrent-servers. Basic stuff which just makes it easier for me to deploy my creations, and those of others.

Re: Docker interactive tutorial

#18
post #16
post #14

Earlier quoted context omitted.

Regarding who is supposed to use it... If you like deploying your apps to a Platform-as-a-Service (PaaS) like Heroku, Google AppEngine, or DotCloud, but wanted to run it on your own infrastructure, then Docker could be for you! It's designed to be a key building block for anyone who wants to create their own PaaS-like service or environment. Why would you need your own PaaS? You might have unique security requirement…

So I'm used to configuring stuff by hand, and now I see a lot of buzz around docker, vagrant, chef, puppet, salt and they seem like glorified shell scripts. Am I missing something?

It's basically what you get when you start your deployment toolchain as simple shell scripts, then make them evolve, add features, and at some point, rewrite from scratch with a "real" programming language. I don't know if that matches your definition of "glorified" though :-)

Re: Docker interactive tutorial

#19
post #15
post #9

Earlier quoted context omitted.

It depends. Do you mind me asking, what is your background/profession? And have you deployed a virtual machine before to run an application?

Im a coder and owner of a small SaaS company. What I do to run applications is this: I fire up a vm or dedicated server on some provider and run my stuff on it. I use Amazon and a couple of other providers.

Ok. That's great. Then let me try to give you some examples #:

Imagine you have setup your SaaS to run from some containers (1 container with your web app, 1 container with your worker, 1 container with your queue and a database somewhere.

Now let's walk through a scenario for a significant new release of your web app:

1) Package your new web app, Launch it for testing (on the same host, cheap) to point to a testing database. 2) Fails? Rebuild, test immediately. 3) Happy? Now relaunch your container to connect to the production database 4) Everything works completely? Now re-route your traffic to the already warmed up container. Chances of failure? Some other ideas: - Package your worker. Run it once (on the same host), more load? run it multiple times, run it on multiple servers. -- it is so much quicker and cheaper than spinning up virtual machines. - So your developer made some changes.. He packages it and you run it. It fails. You now just save the entire container including the last state, logs and everything exactly as you crashed it. And hand that back to him.

Hope it helps.

these examples are based on intended use, because right now the whole development is still moving so fast production deployments are no yet recommended.

Re: Docker interactive tutorial

#20
post #2

The creator here. Please let me know if you have any questions or comments!

Hi dhrp, I assume you work for Dotcloud? Nice job so far. Where do you see this heading to? What's your view of what will happen in the virtualization world? Best,

Oh, and yes, I do work for dotCloud.
Post reply on HN