5 ms·

He explains the problem well, but I yet to see someone who explains the docker solution (into more details) well.

by snird 13y ago

willvarfar 13y ago
I'll try: Previously, to control an environment for an app or set of apps, you either dictated exactly the environment os version and libraries etc, or you tried to run some kind of wrapper like fabric and virtualenv or maven or chef or whatever. And it keeps breaking for real, and developers keep screwing up because they aren't running the exact deployed system. Docker turns that around. It let's you specify the environment exactly, yet also treat that container as an app. It sorts out the versioning (git), and it makes it trivial for all devs to run the stack identically to production. As I've just had to get oracle SDK working troubleshooting on my macbook, I can't say how appealing the docker way sounds.
jamtur01 13y ago
This slide deck has a pretty good explanation of the solution: http://www.slideshare.net/dotCloud/why-docker2bisv4 http://www.slideshare.net/dotCloud/why-docker2bisv4
schnevets 13y ago
I haven't been following Docker too closely, but I think I finally made an apt metaphor from this latest article. There's an old analogy suggesting that Servers:VMs :: Houses:Apartments, as in virtualized servers are separate, individual homes from the same physical asset. With Docker, the metaphor gets extended to a dwelling with more communal space and shared resources (like a hotel or some type of commune). You have one large kitchen, one large laundry room, and a little space for any other amenities, but each room is its own unique dwelling that can utilize any and all of the external utilities. EDIT: Really, the metaphor is better if you use chroot instead of VMs
prodigal_erik 13y ago
It could have been clearer that the author is advocating containers as an alternative to virtual machines for isolating your apps from other users on shared servers. For some reason a lot of other people are advocating containers to isolate your apps from each other on your own server (or VM); there's very little reason to do that unless you have a bunch of poorly managed apps with incompatible dependences which didn't come from your .rpm or .deb library.
secure 13y ago
Maybe my article http://michael.stapelberg.de/Artikel/coreos_and_docker_first_steps http://michael.stapelberg.de/Artikel/coreos_and_docker_first... will increase your understanding :)

He explains the problem well, but I yet to see someone who explains the docker solution (into more details) well.

by snird 13y ago

He explains the problem well, but I yet to see someone who explains the docker solution (into more details) well.

I'll try: Previously, to control an environment for an app or set of apps, you either dictated exactly the environment os version and libraries etc, or you tried to run some kind of wrapper like fabric and virtualenv or maven or chef or whatever. And it keeps breaking for real, and developers keep screwing up because they aren't running the exact deployed system. Docker turns that around. It let's you specify the environment exactly, yet also treat that container as an app. It sorts out the versioning (git), and it makes it trivial for all devs to run the stack identically to production. As I've just had to get oracle SDK working troubleshooting on my macbook, I can't say how appealing the docker way sounds.

jamtur01 13y ago

This slide deck has a pretty good explanation of the solution: http://www.slideshare.net/dotCloud/why-docker2bisv4 http://www.slideshare.net/dotCloud/why-docker2bisv4

schnevets 13y ago

I haven't been following Docker too closely, but I think I finally made an apt metaphor from this latest article. There's an old analogy suggesting that Servers:VMs :: Houses:Apartments, as in virtualized servers are separate, individual homes from the same physical asset. With Docker, the metaphor gets extended to a dwelling with more communal space and shared resources (like a hotel or some type of commune). You have one large kitchen, one large laundry room, and a little space for any other amenities, but each room is its own unique dwelling that can utilize any and all of the external utilities. EDIT: Really, the metaphor is better if you use chroot instead of VMs

prodigal_erik 13y ago

It could have been clearer that the author is advocating containers as an alternative to virtual machines for isolating your apps from other users on shared servers. For some reason a lot of other people are advocating containers to isolate your apps from each other on your own server (or VM); there's very little reason to do that unless you have a bunch of poorly managed apps with incompatible dependences which didn't come from your .rpm or .deb library.

secure 13y ago

Maybe my article http://michael.stapelberg.de/Artikel/coreos_and_docker_first_steps http://michael.stapelberg.de/Artikel/coreos_and_docker_first... will increase your understanding :)