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

Where should we set Environment="KUBELET_EXTRA_ARGS=--feature-gates=DevicePlugins=true" in minikube #2605

Closed
yoshihingis opened this issue Mar 15, 2018 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@yoshihingis
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Only Question

Please provide the following details:

Environment:

Minikube version (use minikube version):0.24.1

  • OS (e.g. from /etc/os-release):Ubuntu16.04LTS
  • VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName):--VM-driver=none
  • ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
  • Install tools:
  • Others:
    The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):Kubernetes version=1.8 ,Nvidia-docker V2
minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver": 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:
I used minikube and nvidia-docker V1, I could create GPU pod.
Now I tried to create GPU pod by minikube and nvidia-docker2.
But we set "Environment="KUBELET_EXTRA_ARGS=--feature-gates=DevicePlugins=true",when we use nvidia-docker2.
If we use kubeadm, we set it at /etc/systemd/system/kubelet.service.d/10-kubeadm.conf.
But I think that minikube does not use kubeadm.
Hence I want to known where I have to set "Environment="KUBELET_EXTRA_ARGS=--feature-gates=DevicePlugins=true"?

I'd really appreciate it if you will give me any advices soon.

@fabiand
Copy link
Contributor

fabiand commented Mar 20, 2018

The following works for me:

minikube start --feature-gates=DevicePlugins=true --vm-driver kvm2

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 18, 2018
@aclowkey
Copy link

@fabiand didn't work for me..

@fabiand
Copy link
Contributor

fabiand commented Jun 27, 2018

@aclowkey what minikube and k8s versions are you using?

@aclowkey
Copy link

@fabiand I solved this by adding --default-runtime=nvidia to the docker service conf.

@rohitagarwal003
Copy link
Member

Hello,
I have a PR that adds GPU support to minikube: #2936. It would be really helpful if people on this thread try it out. The instructions are in the PR.
Thank you!

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 27, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants