support minikube with --vm-driver=none
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Currently, if you start minikube with --vm-driver=none, Tilt does not work properly.
Seems to be some problem with how it's using minikube docker-env, needs investigation
Reported by Jonas in the k8s.slack.io #tilt channel
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing Tilt with minikube started using --vm-driver=none, then inspect the handling of the minikube docker-env entry point. Determine why Docker environment setup does not work in this mode and verify that Tilt operates correctly afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100