What Do We Do at Weaveworks?

Since I made the jump from finance to startups this year, the first question anyone asks is “What are you doing now, Bryan?”. “I work at a startup, building overlay networks and other tools for Linux Containers”. “Really? What’s that...

What We Do! (Via some slides from operatingsystems.io)

Today I spoke at operatingsystems.io – an extremely interesting event as it turned out.  Lots of great speakers, on top form, including no less than three on userland networking.  I spoke about the bigger picture, with reference...

Using Puppet, Weave and Docker in Production

Today on the Weave Blog, we welcome Hugh Esco back for another guest post.  About six weeks ago, Hugh wrote about migrating his applications to a new data centre using Docker and Weave.  As part of that work, Hugh wrote a Puppet...

Life and Docker Networking

“Life moves pretty fast. If you don’t stop and look around once in a while, you could miss it.” In this post, we’ll take a break from talking about Weave and instead have a look around at the emerging set of proposals for Docker...

Have You Met weaveDNS?

Today we’re releasing a preview of weaveDNS: a distributed DNS service for your weave network. As with DNS in general, the main use of weaveDNS is to be able to refer to things by name rather than address. For instance, a database...

Using Weave and Docker to Enable a Visi Spark cluster

Thank-you very much to Dave Pollak for offering this guest post, cross-posted and thus also available on his blog. You have probably come across Dave’s work before – he is among other things the founder of the Scale web framework...

Deploying Riak with Docker, Clocker and Weave

Another quick use case example, following on from the recent Clocker integration of Weave.  In this deck, Cloudsoft’s founders show how the same combination of Clocker, Docker and Weave, can be used to manage Riak as a guest workload...

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...