

Happy Birthday Docker - julien421
http://blog.docker.io/2014/03/happy-birthday-docker/

======
dchuk
I realize this is hard to ask for at this stage because Docker is still
rapidly evolving, but all I want is a thorough book/tutorial/guide/screencast
that walks me through the process of barely understanding Docker to using it
for my web apps.

I know that I will want to use this in the future, I just can't be bothered to
learn yet-another-thing given how fast everything changes nowadays.

Is anyone writing a book on Docker? Tutsplus.com screencast series? Udemy
course?

~~~
shykes
Yeah, a full end-to-end explanation of how Docker can help you is one of the
things we need to get better at. A full revamp of the documentation is
underway :)

There's a book being written at
[http://dockerbook.com/](http://dockerbook.com/)

There's also a really nice online tutorial at
[https://www.docker.io/gettingstarted/](https://www.docker.io/gettingstarted/)

~~~
dchuk
Thanks for the links!

------
shykes
That video of the project's activity over time is pretty awesome and almost
brought a tear to my eye :)
[https://www.youtube.com/watch?v=FCiS812oRU8](https://www.youtube.com/watch?v=FCiS812oRU8)
(link didn't work for me on iOS)

~~~
gabemart
It's a really impressive visualization. Does anyone know how it was made?

~~~
julien421
We used Gource:
[https://code.google.com/p/gource/](https://code.google.com/p/gource/)

~~~
nodesocket
On OS X you can install with:

    
    
        brew install gource

------
aus_
I work for a large financial company. At our shop, we are currently building
out an internal cloud infrastructure where we build on too of the OpenStack
API to provide users with self service deployment much like AWS.

In order to deploy to production, we mandate a process requiring users to have
an existing chef recipe before any production guest can be deployed. We also
restrict logins to existing production nodes unless there is an emergency.
(This attempts to keep configuration management entropy to a minimum.) all of
this works ok, but I think it could be better with Docker.

In a few weeks, I have a chance to present a new idea to senior executives.
I'd like to pitch Docker, at least as something to keep an eye on. Any
thoughts on what points I should drive home?

~~~
jschorr
Offhand, the major benefits for your use case seem to be:

\- Speed and Flexibility: Extremely quick turn around time from development to
production; Docker images usually start in under 10s and multiple images can
be run concurrently. If a user needs to update their running service(s), they
can even have multiple versions running at the same time behind something like
HAProxy (which itself could be in another Docker container), allowing real-
time migration.

\- If your users build their images and test them on their own machines, they
can then deploy the same images to your production machines with the knowledge
that (barring unusual circumstances) they will have the same exact image and
dependencies running there. This means no need to write a recipe, _less_
worries about security, and more freedom for your users to use whatever libs
they deem necessary (assuming such freedom is allowed).

\- If running images directly is not doable for security reasons, your users
could use Dockerfiles [1] which still allow you the benefits of Docker but
with the ability to review all commands used to create the image. They can
even be built in real-time off of GitHub pushes [2] (disclosure: I'm a co-
founder at Quay.io)

[1]
[http://docs.docker.io/en/latest/reference/builder/](http://docs.docker.io/en/latest/reference/builder/)
[2] [http://blog.devtable.com/2014/03/link-your-quayio-
repositori...](http://blog.devtable.com/2014/03/link-your-quayio-repositories-
to-github.html)

------
shykes
It's worth noting that as of yesterday the Docker index
([https://index.docker.io](https://index.docker.io)) now offers github-style
paid features. You can host private docker images, tie them to your source
repo so that they are automatically rebuilt from source, trigger web hooks on
new versions, etc.

[http://blog.docker.io/2014/03/introducing-private-repos-
webh...](http://blog.docker.io/2014/03/introducing-private-repos-webhooks-and-
more/)

------
nickstinemates
Having been @ Docker for about 9 months, all I can say is I am blown away by
the incredible involvement from the community and the vibrant ecosystem that
has been created as a result.

While it has been an amazing year, I am even more excited every day about
future prospects and momentum we're collectively building in the industry.
This is only the beginning.

------
thu
Memories !

I thought I have started to look into Docker in April last year. To make sure
I didn't make up things, I looked into my git logs. The first reference to
Docker in the commit message is:

    
    
        Author: Vo Minh Thu <noteed@gmail.com>
        Date:   Sun May 5 23:21:51 2013 +0300
    
            Run ssp-build inside docker
    

ssp is the name I used for Assertive, which was supposed to be a hosted
Continuous Integration service for the OpenERP community. ssp-build is spawned
inside Docker by a worker process. I put it on hold since around May although
I put it online a few days ago (Here is an example of what it does:
[http://assertive.io/build/1](http://assertive.io/build/1)).

Actually I have a first mention of Docker in my TODO.md file dating back to
March 29 !

Assertive will be generalized and will be coupled to
[https://reesd.com](https://reesd.com) (that's the reason I went to put it
online a few days ago).

Docker was my first practical exposure to Linux containers. Thanks a lot for
making it a great open source project !

------
gabrtv
The project is moving so fast it warps time. Hard to believe it's only been a
year. Big congrats to the team.

------
alecsmart1
I've been reading about Docker for a while. But am unable to wrap my head
around it. I've gone through the samples and I only see it good for creating
SaaS apps. Can someone please correct? What am I missing? What is the brouhaha
all about?

~~~
j_s
Simplistically: if you deploy to Linux, Docker provides 90%+ of the benefits
of virtualization without the performance penalty.

~~~
brokenparser
And without the security benefits of proper virtualisation, too. At least lxc
since recently has the ability to run containers as a regular user, but I'll
stick to KVM guests secured with MLS policies for now.

~~~
nickstinemates
Why not combine the two and get the value of both? And, a reminder, you can
still use LXC with Docker. It's fully supported.

~~~
brokenparser
Because the guests have their own SELinux policies. Docker containers don't
come with policies, but if it would support running containers under a user
account I could at least restrict each to their own category so that
theoretically a chmod -R 777 / (inside a container) and access to the host
wouldn't compromise other containers (unless the kernel is exploitable, in
which case KVM would still win).

~~~
nickstinemates
Maybe we're talking past each other here, but, Dan Walsh, author of SELinux,
is working to bring SELinux natively to libcontainer / docker.

I'd love to talk more about your needs and how we can help. My email is always
open - nick@docker.com

------
CSDude
I have been using Docker to grade HW submission since October, in a more
disposable and safer way, and I am building an automated system around it,
kudos to Docker and the team

~~~
nickstinemates
That is amazing. Can we talk more about it?

We also have a ton of people for you to talk to / benefit from if you're
interested in that.

nick@docker.com

~~~
Hortinstein
please make this public if it happens!

~~~
CSDude
I will, contact me if interested mustafa91 at gmail

