-
Notifications
You must be signed in to change notification settings - Fork 932
Description
What
metaflow-dev up executes minikube tunnel as a background process (&), so when minikube tunnel requests a password ([sudo] password for user:) it's not possible to type it in.
Workaround
Run the (undocumented) metaflow-dev setup-minikube, then (undocumented) metaflow-dev tunnel, type in the password, before finally running metaflow-dev up in a separate terminal.
Notes
The minikube handbook calls out this sudo access as an issue, and suggests allowing minikube passwordless sudo access, but I don't think this can work for metaflow-dev as a general solution, since it downloads minikube to an unpredictable location.
I tried minikube tunnel --rootless, but it still asks for sudo password, so "rootless" must be referring to something else.
I do note that my "Hello World"-style example flow can run even if I comment out the tunnel. I'd be curious to know what the use-case is for the tunnel - the minikube docs are a bit unclear to me, and the metaflow git history and original pull request doesn't explain.