Weave – The Docker Network
github.com
Weave – The Docker Network
1–10 of 65 posts
Re: Weave – The Docker Network
#2These are the same people who built RabbitMQ.
Re: Weave – The Docker Network
#3These are the same people who built RabbitMQ.
:-) The founding team, yes.
Re: Weave – The Docker Network
#4as someone who is more developer than ops, I feel like the docker stuff is still changing fast and that the way you would use docker today will be very different a year from now; but that containers seem to be the way of the future - if I have no pressing need to change my server architecture does it make sense to wait for things settle or would it be more beneficial to get in and learn now and experience the changes and why they were necessary?
Re: Weave – The Docker Network
#5These are the same people who built RabbitMQ.
RabbitMQ has always been an extraordinarily good piece of software, from the very first versions. I think this is very good news for anyone using Docker.
Re: Weave – The Docker Network
#6as someone who is more developer than ops, I feel like the docker stuff is still changing fast and that the way you would use docker today will be very different a year from now; but that containers seem to be the way of the future - if I have no pressing need to change my server architecture does it make sense to wait for things settle or would it be more beneficial to get in and learn now and experience the changes…
It is definitely changing fast, but that is not a reason to wait before trying out the technology in order to learn about it. If nothing else, the community will welcome your feedback :-)
Re: Weave – The Docker Network
#7as someone who is more developer than ops, I feel like the docker stuff is still changing fast and that the way you would use docker today will be very different a year from now; but that containers seem to be the way of the future - if I have no pressing need to change my server architecture does it make sense to wait for things settle or would it be more beneficial to get in and learn now and experience the changes…
precisely because you're a developer you whould embrace docker with open arms.
Because docker removes all the trouble of running applications that you need for your development: databases, application servers, queues...
I love the fact that I can focus on my code and not on all those details that stole so much of my time.
Re: Weave – The Docker Network
#8as someone who is more developer than ops, I feel like the docker stuff is still changing fast and that the way you would use docker today will be very different a year from now; but that containers seem to be the way of the future - if I have no pressing need to change my server architecture does it make sense to wait for things settle or would it be more beneficial to get in and learn now and experience the changes…
precisely because you're a developer you whould embrace docker with open arms. Because docker removes all the trouble of running applications that you need for your development: databases, application servers, queues... I love the fact that I can focus on my code and not on all those details that stole so much of my time.
I'd like to see a post/writeup (or even an essay!) on how to do the magic "backing services" (http://12factor.net/backing-services) with Docker. And that's where I find Deis and other Docker orchestration systems lacking very much.
Sure, you can run MySQL in Docker, but it's a far cry from running it on native xfs with aligned partitions and whatever fancy you feel configuring. And since docker containers are very reusable, whereas backing data is by default should be persistent, my impression is that it's too easy to accidentally remove a docker container.
Re: Weave – The Docker Network
#9I hope all of these Docker overlay networks start using the in-kernel overlay network technologies soon. User-space promiscuous capture is obscenely slow.
Take a look at GRE and/or VXLAN and the kernels multiple routing table support. (This is precisely why network namespaces are so badass btw). Feel free to ping me if you are working on one of these and want some pointers on how to go about integrating more deeply with the kernel.
It's worth mentioning these protocols also have reasonable hardware offload support, unlike custom protocols implemented on UDP/TCP.
Re: Weave – The Docker Network
#10Earlier quoted context omitted.
precisely because you're a developer you whould embrace docker with open arms. Because docker removes all the trouble of running applications that you need for your development: databases, application servers, queues... I love the fact that I can focus on my code and not on all those details that stole so much of my time.
I'd like to see a post/writeup (or even an essay!) on how to do the magic "backing services" ( http://12factor.net/backing-services ) with Docker. And that's where I find Deis and other Docker orchestration systems lacking very much. Sure, you can run MySQL in Docker, but it's a far cry from running it on native xfs with aligned partitions and whatever fancy you feel configuring. And since docker containers are very…
Nothing is stopping you from running MySQL in Docker on native xfs with aligned partitions: bind-mount whatever partition you want into the container by defining a volume in Docker.
This will be persistent, and will survive when you destroy the container. I use this to e.g. share a /home directory between a dozen experimental dev container I use to run my various projects - each container ensures I keep track of exact dependencies for each individual project, while I get to have a nice "comfortable" swiss-army-knife container with my dev tools and all all project files.
I also run a number of database containers which use volumes where I bind mount host directories to ensure persistence so I can wipe and rebuild the containers themselves without worrying about touching data.