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

the "none" driver does not use correct container runtime #3295

Closed
afbjorklund opened this issue Nov 4, 2018 · 3 comments
Closed

the "none" driver does not use correct container runtime #3295

afbjorklund opened this issue Nov 4, 2018 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@afbjorklund
Copy link
Collaborator

BUG REPORT

Currently the "none" driver is hardcoded to look for docker: cb8d3c0

It should look at the --container-runtime, and adjust accordingly...

(From #3153)

@afbjorklund afbjorklund changed the title the "none" driver always requires docker the "none" driver does not use correct container runtime Nov 4, 2018
afbjorklund added a commit to afbjorklund/minikube that referenced this issue Nov 6, 2018
afbjorklund added a commit to afbjorklund/minikube that referenced this issue Nov 6, 2018
@tstromberg tstromberg added the kind/bug Categorizes issue or PR as related to a bug. label Nov 6, 2018
afbjorklund added a commit to afbjorklund/minikube that referenced this issue Nov 7, 2018
@balopat balopat closed this as completed Nov 13, 2018
@tstromberg
Copy link
Contributor

@afbjorklund appears to be working on this.

@jayunit100
Copy link
Member

any updates here ?

@afbjorklund
Copy link
Collaborator Author

As long as you use --container-runtime=cri-o, it should work now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants