4 ms·
Thanks, that's exactly the sort of thing I was hoping to learn from the HN comments. In the post you link above, it seems like you're mainly comparing Docker t
by wpietri 12y ago
Thanks, that's exactly the sort of thing I was hoping to learn from the HN comments.
In the post you link above, it seems like you're mainly comparing Docker to traditional, non-virtualized setups. Do you (or does anybody) have thoughts on comparing it to virtualized environments? I recently experimented with Xen as a way to isolate services, and it seemed awfully heavy; does Docker end up being a lighter burden?
- lojack 12y agoIt's lighter in the sense that it should require less resources to keep each container running, but comparable in the sense that you still need to orchestrate how services connect and how each container is configured.
- geerlingguy 12y agoThis, exactly. I've heard many people talking about how Docker will put an end to a thousand different problems, especially regarding configuration management... But it really won't. You still need to be able to configure everything inside the container (thus the need for a CM tool), and then also the environment and infrastructure inside which the containers live (thus the need for infra management tools). Docker really doesn't make infrastructure management markedly easier—just faster, more flexible, and slightly more powerful. It's one layer of abstraction over a VM, IMO, and that's a good thing, but carries with it it's own set of complexities.
- skrebbel 12y ago> You still need to be able to configure everything inside the container (thus the need for a CM tool) I'm missing something, but in what scenarios would you need to do something more complex than what can be expressed in a few RUN and ADD commands in a Dockerfile? My limited experience is that indeed, orchestration is still completely needed. We underestimated that and now we have a bunch of hacky shell scripts that build and start and stop docker containers at various moments. But the docker containers themselves are pretty simple.
- geerlingguy 12y agoIt depends on what you're doing inside the containers themselves. If you're simply pulling from a git repo to update a code checkout, and installing one or two things via apt/yum, shell script/RUN isn't so bad. If you're approaching containers more like 'lightweight VMs', the string of RUN commands gets unmaintainable, fast. That can indicate some deeper problems, but in some circumstances (and especially when making updates to your container images), using configuration management for individual containers can be helpful for the same reasons even CM-ifying a small single-purpose standalone VM can.
- deleted 12y ago[deleted]
- mattjaynes 12y agoThanks. Yeah, most of the misconceptions seem to come from folks without previous experience with self-managed virtualized setups. Those that have had that experience usually already understand the complexities involved. I'd also love to hear more stories about Docker vs the other virtualized setups. It generally seems to be a dramatic improvement in usability, performance, etc, but I'd love to hear more about the specifics from those who have made the switch. Here's a few production users: http://www.docker.com/resources/usecases/ http://www.docker.com/resources/usecases/ http://blog.docker.com/2013/12/baidu-using-docker-for-its-paas/ http://blog.docker.com/2013/12/baidu-using-docker-for-its-pa...
- mikko-apo 12y agoWe used Docker for the Hello World Open coding competition. We provided CI for the 2500 teams and also ran the competition using Docker (both on top of AWS EC2 instances). I think that without Docker the implementation would have been a lot more painful and almost impossible given the time constraints we had for the project. Fast starting and fast shutdown of build and test processes allowed us to run CI builds efficiently on a fairly small amount of nodes. This saved us money and also helped to keep the infrastructure manageable. Also the additional level of security was really nice since we were running possibly malicious code from 2500 sources. The malicious part became even more evident when Kevin Mitnick tweeted that he might participate: https://twitter.com/kevinmitnick/status/446359450614378496 https://twitter.com/kevinmitnick/status/446359450614378496 The Docker image repository was also really handy when we ran the races. We needed build the bots only once and then we could just use the prebuilt images on on race nodes. Building the actual base image was fairly painful. We support about 20 different programming languages and also package in quite a few libraries. Once the base image build was fully automatized and we had the Docker related processes fully working, it was almost a revelation on how Docker could improve things over the classical virtual machine approach. I can't wait to try it out on another project :) By the way, the competition finals are today (Tuesday) and streamed live @ https://helloworldopen.com/ https://helloworldopen.com/ (in English and Finnish)
- wpietri 12y agoThat sounds really interesting. Please document it! I'd be especially interested to read about the revelations.
- Alupis 12y agoMy gripes: * half git-syntax/half package manager-syntax is cumbersome to me. * Inability to compile Docker from source without using the Docker Project's provided "black box" binary Docker. * No formal explanation of how to create your own base image from scratch (ie. not using a Docker Project provided base image). * Defaults to storing images in the Docker "cloud" repo. (would have preferred a git-like setup where pushing my images to a repo of my choice was more "normal") * GO Lang is still pretty obscure for most developers, and an interesting choice given the language's youth and likely-hood to change rapidly as it matures. * Docker is built on-top of existing Linux technologies, mainly LXC, making it more-or-less disposable in the future (as someone else figures out how to abstract/manage LXC better) * Docker is mainly built by Dotcloud - a for-profit company. Dotcloud has been very generous in their effort... but, being for-profit, what is their take out of it? (It can't be "just for the goodness of Linux").
- lolo_ 12y ago> * GO Lang is still pretty obscure for most developers, and an interesting choice given the language's youth and likely-hood to change rapidly as it matures. The go authors have committed to keeping major versions stable since v1 and are unlikely to massively change anything. I'm sure much of google's infrastructure is coming to rely on go (and docker!) so they will be as unhappy about such drastic change as others.
- Alupis 12y agoFair enough point about GO Lang, however, should note Docker as a project was started way back when GO's future was... perhaps iffy. Maybe good foresight on the Docker project regarding GO Lang. However, this doesn't excuse the remaining gripes listed above.
- nl 12y agoFair enough point about GO Lang, however, should note Docker as a project was started way back when GO's future was... perhaps iffy. You mean 14 months ago?
- 12y ago