HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ClusterHQ
powerstrip
Python2015–2015
ClusterHQ / powerstrip

powerstrip

Powerstrip: A tool for prototyping Docker extensions

3Distinct people
4Mentions
0Explicit recommenders
295GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Powerstrip: A tool for prototyping Docker extensions

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval4 dated mentions

Observed mentions: 2015-01-29 17:25:36 UTC to 2015-02-05 17:01:32 UTC.

0122015-01-29 12:00:00 UTC to 2015-01-29 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 29, 12:002015-01-29 18:00:00 UTC to 2015-01-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-30 00:00:00 UTC to 2015-01-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-30 06:00:00 UTC to 2015-01-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-30 12:00:00 UTC to 2015-01-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-30 18:00:00 UTC to 2015-01-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-31 00:00:00 UTC to 2015-01-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-31 06:00:00 UTC to 2015-01-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-31 12:00:00 UTC to 2015-01-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-31 18:00:00 UTC to 2015-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-01 00:00:00 UTC to 2015-02-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-01 06:00:00 UTC to 2015-02-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-01 12:00:00 UTC to 2015-02-01 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-01 18:00:00 UTC to 2015-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-02 00:00:00 UTC to 2015-02-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 2, 00:002015-02-02 06:00:00 UTC to 2015-02-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-02 12:00:00 UTC to 2015-02-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-02 18:00:00 UTC to 2015-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-03 00:00:00 UTC to 2015-02-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-03 06:00:00 UTC to 2015-02-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-03 12:00:00 UTC to 2015-02-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-03 18:00:00 UTC to 2015-02-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-04 00:00:00 UTC to 2015-02-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-04 06:00:00 UTC to 2015-02-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-04 12:00:00 UTC to 2015-02-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-04 18:00:00 UTC to 2015-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-05 00:00:00 UTC to 2015-02-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-05 06:00:00 UTC to 2015-02-05 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-05 12:00:00 UTC to 2015-02-05 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 5, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 29, 12:002015-01-29 12:00:00 UTC2015-01-29 18:00:00 UTC101
Jan 29, 18:002015-01-29 18:00:00 UTC2015-01-30 00:00:00 UTC101
Jan 30, 00:002015-01-30 00:00:00 UTC2015-01-30 06:00:00 UTC000
Jan 30, 06:002015-01-30 06:00:00 UTC2015-01-30 12:00:00 UTC000
Jan 30, 12:002015-01-30 12:00:00 UTC2015-01-30 18:00:00 UTC000
Jan 30, 18:002015-01-30 18:00:00 UTC2015-01-31 00:00:00 UTC000
Jan 31, 00:002015-01-31 00:00:00 UTC2015-01-31 06:00:00 UTC000
Jan 31, 06:002015-01-31 06:00:00 UTC2015-01-31 12:00:00 UTC000
Jan 31, 12:002015-01-31 12:00:00 UTC2015-01-31 18:00:00 UTC000
Jan 31, 18:002015-01-31 18:00:00 UTC2015-02-01 00:00:00 UTC000
Feb 1, 00:002015-02-01 00:00:00 UTC2015-02-01 06:00:00 UTC000
Feb 1, 06:002015-02-01 06:00:00 UTC2015-02-01 12:00:00 UTC000
Feb 1, 12:002015-02-01 12:00:00 UTC2015-02-01 18:00:00 UTC000
Feb 1, 18:002015-02-01 18:00:00 UTC2015-02-02 00:00:00 UTC000
Feb 2, 00:002015-02-02 00:00:00 UTC2015-02-02 06:00:00 UTC000
Feb 2, 06:002015-02-02 06:00:00 UTC2015-02-02 12:00:00 UTC000
Feb 2, 12:002015-02-02 12:00:00 UTC2015-02-02 18:00:00 UTC000
Feb 2, 18:002015-02-02 18:00:00 UTC2015-02-03 00:00:00 UTC000
Feb 3, 00:002015-02-03 00:00:00 UTC2015-02-03 06:00:00 UTC000
Feb 3, 06:002015-02-03 06:00:00 UTC2015-02-03 12:00:00 UTC000
Feb 3, 12:002015-02-03 12:00:00 UTC2015-02-03 18:00:00 UTC000
Feb 3, 18:002015-02-03 18:00:00 UTC2015-02-04 00:00:00 UTC000
Feb 4, 00:002015-02-04 00:00:00 UTC2015-02-04 06:00:00 UTC000
Feb 4, 06:002015-02-04 06:00:00 UTC2015-02-04 12:00:00 UTC000
Feb 4, 12:002015-02-04 12:00:00 UTC2015-02-04 18:00:00 UTC000
Feb 4, 18:002015-02-04 18:00:00 UTC2015-02-05 00:00:00 UTC000
Feb 5, 00:002015-02-05 00:00:00 UTC2015-02-05 06:00:00 UTC000
Feb 5, 06:002015-02-05 06:00:00 UTC2015-02-05 12:00:00 UTC000
Feb 5, 12:002015-02-05 12:00:00 UTC2015-02-05 18:00:00 UTC202

What Hacker News says

4 sources
We* love kubernetes, and all the other orchestration frameworks, like Mesosphere, fleet, docker swarm, etc. We see flocker, our open-source project for managing data volumes, running beside these orchestrators. In fact, we've just released another open-source tool called powerstrip (https://github.com/ClusterHQ/powerstrip) which makes it possible to write adaptors for the Docker API so that a user can eventually use Flocker with Kubernetes. Regarding how we are different, we focus only on managing persistent volumes, and as a specialist, will be able to do a lot more than something like kubernetes that is managing the entire application. If I had to guess, what you'd see with kubernetes, mesos, docker, etc is that they all support some basic data movement features, but if you want something more customized, like live migration, or true
Read the rest
Disaster Recovery, you'd use Flocker, along side your orchestrator of choice. *in case it wasn't clear, I work at ClusterHQ
In ClusterHQ raises $12M Series A from Accel, Canaan to build data layer for Docker
Hey, Luke here, CTO at ClusterHQ. As well as being proud of this company milestone, I can't wait to get powerstrip (https://github.com/clusterhq/powerstrip) and flocker (https://github.com/clusterhq/flocker) working together so that we can start composing flocker with other docker ecosystem tools. It will be a great day that you can have a docker swarm with flocker and weave. Or kubernetes with flocker and socketplane. Or even mesosphere with rancher and calico ;) We've got some pretty neat demos of powerstrip prototypes up here, fwiw: http://clusterhq.com/blog/powerstrip-prototype-docker-extens... Any questions just shout! Cheers, Luke
In ClusterHQ raises $12M Series A from Accel, Canaan to build data layer for Docker
I'm involved as an independent collaborator again in Docker's internal extension efforts, and after I saw this I got ClusterHQ looped in to that working group. Then we talked about collaborating on a Go port of Powerstrip, so I'm working on that here: https://github.com/ClusterHQ/powerstrip/tree/golang We're also planning to combine the Docker event stream plugin system I prototyped previously into Powerstrip: https://github.com/progrium/docker-plugins And ultimately, eventually, we'll have native extension support in Docker that allows much more extensibility, but all this is a good first step IMO.
In Powerstrip: prototype Docker extensions today

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.