-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
eval (minikube -p minikube docker-env) doesn't work in fish-shell #6595
Comments
Looks like both code and test was changed (semicolon removed), so looked intentional... @tstromberg ? |
Still broken, with anders@anders-ThinkPad:~$ fish
Välkommen till fish, det vänliga interaktiva skalet
Skriv help för instruktioner om hur man använder fish
anders@anders-ThinkPad ~> minikube docker-env
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.100:2376"
export DOCKER_CERT_PATH="/home/anders/.minikube/certs"
export MINIKUBE_ACTIVE_DOCKERD="minikube"
# To point your shell to minikube's docker-daemon, run:
# eval $(minikube -p minikube docker-env)
anders@anders-ThinkPad ~> eval $(minikube -p minikube docker-env)
$(...) is not supported. In fish, please use '(minikube)'.
fish: eval $(minikube -p minikube docker-env)
^
anders@anders-ThinkPad ~> fish --version
fish, version 2.2.0
anders@anders-ThinkPad ~> minikube version
minikube version: v1.7.3
commit: 436667c819c324e35d7e839f8116b968a2d0a3ff Apparently it doesn't set SHELL, so that is why the detection fails. But if you try, then it actually gets worse (and definitely fails...)
Was this what you were seeing too, @kppullin ? |
@afbjorklund my output is similar, but without the My login shell is set to fish, in which case the |
Fixed in v1.8.0 |
The command doesn't do what it's expected in fish-shell, may be related to: #6540
The exact command to reproduce the issue:
eval (minikube -p minikube docker-env)
The full output of the command that failed:
Quick workaround is to just copy and paste the set commands and run them manually:
Something like:
The operating system version: macOS 10.14.5
The text was updated successfully, but these errors were encountered: