Skip to content
This repository has been archived by the owner. It is now read-only.
Container data volume manager for your Dockerized application
Branch: master
Clone or download
Pull request Compare This branch is 4 commits ahead of ClusterHQ:master.
tomprince Merge pull request #1 from ScatterHQ/scatterhq-readme
Point README at ScatterHQ.

Author: @tomprince
Reviewer: @wallrj
Latest commit 9dd5214 Jan 9, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
benchmark A couple more order sensitive tests. Dec 8, 2016
requirements update-requirements Dec 17, 2016
.gitattributes Use python-versioneer. May 12, 2014
LICENSE Updated copyright in LICENSE file Jan 13, 2016
build.yaml Don't overwrite the SSH key everytime Dec 21, 2016



Flocker is an open-source Container Data Volume Manager for your Dockerized applications.

By providing tools for data migrations, Flocker gives ops teams the tools they need to run containerized stateful services like databases in production.

Unlike a Docker data volume which is tied to a single server, a Flocker data volume, called a dataset, is portable and can be used with any container, no matter where that container is running.

Flocker manages Docker containers and data volumes together. When you use Flocker to manage your stateful microservice, your volumes will follow your containers when they move between different hosts in your cluster.

You can also use Flocker to manage only your volumes, while continuing to manage your containers however you choose.

About Us

Flocker is being maintained by ScatterHQ. We are a small team of engineers with experience running distributed systems and many of us are core contributors to the Twisted project.

This project is under active development; version 1.0 was released on June 17th, 2015. Contributions are welcome. If you have any issues or feedback, you can talk to us. We're looking forward to working on this project with you.


You can read more about installing Flocker, follow a tutorial and learn about the features of Flocker and its architecture in the Flocker docs.

Feature Requests

If you have any feature requests or suggestions, we would love to hear about them. Please send us your ideas by filing a GitHub issue.


Flocker's test suite is based on unittest and Twisted Trial. The preferred way to run the test suite is using the command trial flocker. Flocker also includes a tox configuration to run the test suite in multiple environments and to run additional checks (such as flake8) and build the documentation with Sphinx. You can run all of the tox environments using the command tox.

Flocker is also tested using continuous integration.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.