November 03, 2015
Docker networking 1.9 and Weave technical deep-dive
This is a technical follow up to the previous post, Life and Docker Networking – One year On. Please note that our goal here, shared with Docker, is to make the customer experience as straightforward as possible. Do get in touch if you...
July 16, 2015
Bridge over Troubled Weavers
When we originally shipped Weave Net, there were a couple of things that people looked for extra help with: giving each container a unique IP address running containers using the Docker CLI or remote API, not via our weave script...
July 14, 2015
I Quadrupled the Speed of Our Container Test Rig in a Day
Spoiler: this post is about Docker storage drivers. Not volume storage drivers, but how Docker implements the files inside every container.Background: as part of our drive to deliver high-quality software, we maintain a set of...
July 13, 2015
Testing Times at Weaveworks
We like continuous integration and testing at Weaveworks. This blog post tells the story of the journey we have been through, the tools and technologies we use, what worked and what didn’t, and the lessons we’ve learned. A few months back,...
June 22, 2015
Weave as a Docker Network Plugin
The Weave plugin gives you a closer integration with Docker: docker inspect --format=’{{.NetworkSettings.IPAddress}}’ $WOVEN_CONTAINER A while ago I reported on a proof of concept that made Weave act as a Docker extension. Much of the...
April 14, 2015
My Container Won't Stop on Ctrl-C, and Other Minor Tragedies
At Weaveworks, we containerise as much as possible, to simplify packaging and deployment. So, most of the time, whatever you ask our software to do will run inside a container. One day while testing, one step of network set-up got stuck,...
October 31, 2014
Why Do We Have a Script that Wraps the 'docker' Command?
We’ve heard this question quite a few times. Sometimes it’s a reaction to a problem, like “I already have this other script that runs the Docker command, so it’s inconvenient to have to run your script instead”. So I thought I...