Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oswitch as a Docker extension (with powerstrip)? #22

Open
bmpvieira opened this issue Mar 4, 2015 · 2 comments
Open

oswitch as a Docker extension (with powerstrip)? #22

bmpvieira opened this issue Mar 4, 2015 · 2 comments
Labels

Comments

@bmpvieira
Copy link
Member

Right now it seems everyone is solving Dockers problems by wrapping the docker cli (e.g., weave (networking), flocker (data mobility)). The problem is that all those wrappers become incompatible with each other. Last night, me and Chris went to a Docker meetup (biggest ever) where they presented powerstrip, which aims to be the way to build Docker extensions (and hopefully someday merged into Docker). What it does is wrapping Docker once to provide prehooks and posthooks so that extensions can be built without wrapping Docker again.
I think it's worth checking this and thinking a bit about it while we are still in early stage.

@yeban yeban added the question label Nov 11, 2015
@yeban
Copy link
Contributor

yeban commented Nov 14, 2015

@bmpvieira Can this or any other docker-extension scheme make oswitch work in Kitematic? Like, you pull an image in Kitematic and it gets run through oswitch?

@bmpvieira
Copy link
Member Author

@yeban Powerstrip just allows some Docker wrappers out there to play nice with each, while we wait for Docker "plugins" to become the definitive solution. Not sure how Kitematic could run something like oswitch after downloading an image, maybe some kind of Kitematic extension? Maybe ask here: https://github.com/kitematic/kitematic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants