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

support multiple container engines on the host #154

Open
BenTheElder opened this issue Dec 6, 2018 · 3 comments

Comments

@BenTheElder
Copy link
Member

commented Dec 6, 2018

#151 should bring initial support for podman via @rhatdan

This should mostly be a drop in replacement.

We should further clean up the code base a bit to help with this sort of thing. We've mostly but not quite isolated the container runtime functionality.

/assign
/assign @rhatdan

/kind feature
/kind cleanup
/priority important-longterm

related: #153 is the same thing, but within the nodes

@BenTheElder

This comment has been minimized.

Copy link
Member Author

commented Feb 24, 2019

There's now a container package with docker as a subset, and we're working on plumbing through optional arguments to the cluster better, I expect to get limited podman support based on these pretty soon.

@BenTheElder

This comment has been minimized.

Copy link
Member Author

commented Feb 24, 2019

We're also targeting CRI functionality explicitly: https://kind.sigs.k8s.io/docs/design/principles/#target-cri-functionality

@BenTheElder

This comment has been minimized.

Copy link
Member Author

commented Mar 18, 2019

Currently working on moving more of the flags (ports) behind abstractions borrowed from CRI.
I'd like to isolate all knowledge of docker / podman style flags to pkg/container/... by the next milestone, at which point we should be able to do podman support properly with it's own implementation of all functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.