sudo: eval: command not found

I have installed minikube on my system and minikube start works as expected for me. When I want to use local docker images and hence trying to run sudo eval $(minikube docker-env).

This gives me an error:

sudo: eval: command not found

Any guidance or solution for this? I am running this on MacOS Mojave.

6 Answers

You use sudo eval $(minikube docker-env), sudo: eval: command not found this means eval not found. eval is an built-in in shell, so when sudo without -s it will surely tell you this error, like next:

shubuntu1@shubuntu1:~/777$ sudo eval sudo: eval: command not found shubuntu1@shubuntu1:~/777$ sudo -s eval shubuntu1@shubuntu1:~/777$ 

• If you want to execute with root account:

  $ sudo -s -H $ eval $(minikube docker-env) 

• If you just intend to execute with current account:

  $ eval $(minikube docker-env) 

Ran into same issue while setting up the jenkins workflow. Below solution worked for me:

Instead of:

eval $(minikube docker-env) 

Try using:

sudo -s eval $(minikube docker-env) 

Others coming here could get this error for an entirely different reason as the accepted answer. In my case the minikube cluster was not running. The error you get in this case is also command not found.

Just run the command: minikube docker-env and if you get the error: The control plane node must be running for this command just start it using minikube start and re-run the command eval $(minikube docker-env). It should work this time.

For me the trouble was in quotes: instead of eval $( "${cm}" )

put this

eval $"( "${cm}" )" 

In my case it was spacing issues with non-breaking spaces. You can visualize these using following command:

LC_ALL=C cat -v .zshrc 

removing that non-breaking space "M-BM- " solved my problem.

Thanks to this stackoverflow solution

echo ssh-agent -s > .tmp_ssh_agent

source .tmp_ssh_agent

this worked for me instead of eval (May help you)