sudo: garden: command not found

[marcus-sa]

Bug

Current Behavior

Unable to run garden get status as instructed in your Quick Start guide due to you not supporting sudo:

$ sudo garden get status
sudo: garden: command not found

sudo is required when using minikube with no drivers kubernetes/minikube#3760

Expected behavior

Being able to run garden as sudo user.

Environment

garden version: 0.10.0

[edvald]

Hey @marcus-sa. I believe the issue is not that Garden can't be run as sudo, but rather that sudo garden can't find the garden binary. If you run sudo <full-path-to-garden> or symlink /usr/local/bin/garden to where you have Garden installed, it should work fine.

I'm curious though, why do you need to run Garden with sudo?

[marcus-sa]

@edvald hey you're probably right.
As I wrote, starting minikube with no driver's locally requires sudo explicitly for accessing its config file in ones home directory.
Even though I ran chmod -R 777 . on it, unfortunately still failed.

This happens because

garden/garden-service/src/plugins/kubernetes/local/minikube.ts

Line 16 in ed0233b

const minikubeEnv = await execa.stdout("minikube", ["docker-env", "--shell=bash"])

Isn't supported with no driver's specified, even though it uses docker as the container.

See these issues:
kubernetes/minikube#2443
kubernetes/minikube#2575
GoogleContainerTools/skaffold#112

As you can see in the first issue, arguments passed after minikube actually isn't needed when there's no vm driver.

[edvald]

Ah, interesting. I guess we'd need to explicitly catch that error message or otherwise check which VM driver is in use. Should be easy to do, I'll flag it for our next update.

[eysi09]

Fixed with #910 (assuming the original problem with sudo was a none-issue).

[ghostnet2000]

cd to where you have Garden installed, and run chmod +x garden