jx install cannot find tiller when installing on Minkube or Docker for Mac

[i386]

Ive installed Docker for Mac CD version 18.02.0-ce-rc2-mac51 (22446) and started Kubernetes from it.

pounder:~ jdumay$ jx install
Lets set up a git username and API token to be able to perform CI / CD

? Do you wish to use i386 as the GitHub username for CI/CD pipelines: Yes
Cloning the Jenkins X cloud environments repo to /Users/jdumay/.jenkins-x/cloud-environments
Counting objects: 200, done.
Compressing objects: 100% (42/42), done.
Total 200 (delta 31), reused 53 (delta 22), pack-reused 136
helm repo add jenkins-x http://chartmuseum.build.cd.jenkins-x.io
"jenkins-x" has been added to your repositories
rm -rf secrets.yaml.dec
helm repo add jenkins-x http://chartmuseum.build.cd.jenkins-x.io
"jenkins-x" has been added to your repositories
helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "jenkins-x" chart repository
...Successfully got an update from the "incubator" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈ 
helm install jenkins-x/jenkins-x-platform --name jenkins-x -f ./myvalues.yaml -f ./secrets.yaml --version 0.0.43 
Error: could not find tiller
make: *** [install] Error 1
Error: Command failed  make install
error: exit status 2
pounder:~ jdumay$ which tiller
/usr/local/bin/tiller

For reference I have the following installed via brew

pounder:~ jdumay$ brew list
docker-machine	gettext		icu4c		kubernetes-cli	libev		watch
draft		git		jx		kubernetes-helm	node

[michaelneale]

I don't think k8s on docker4mac is supported yet (it is missing a few things that minikube has, unless you know otherwise)

[michaelneale]

Also - the installation instructions are not good now in the readme. There is a lot of assumption about minikube (and hyperkit) which is not called out, and causing some grief.

[i386]

@michaelneale nope this is still a problem with minikube provided Kubernetes

[michaelneale]

@i386 ack - have updated accordingly

[amuniz]

Did you retry jx install after a few seconds/minutes? I've seen this before, the issue is that helm init was called just a few seconds before helm install jenkins-x/jenkins-x-platform and Tiller is not completely started at that point.

Use helm version to check Tiller is ready in the cluster and then retry jx install - not saying this is a fix, but a workaround.

[rawlingsj]

How did you create the minikube cluster? The docs need some work now that we use jx but you should be able to just run

jx create cluster minikube

from a clean state where there's no existing minikube created.

Alternatively if you have minikube running already you can:

jx init
jx install

jx init will initiate the cluster with helm, draft and an ingress controller. FWIW it will also wait for pods to be running so there should be no timing issues.

I'll try and get to updating the docs later today.

BTW we also now have a jx create cluster gke you can test out if you have a google account and google cloud project available. The same command on AKS is being worked on.

[amuniz]

I think I did jx install directly on an existent minikube cluster I created by myself. So that might be the cause of the timing issues I observed.

[michaelneale]

@rawlingsj I did it from a total clean slate - latest minikube, using jx create cluster minikube and it failed.

ran jx init again and jx install, only for it to fail with:

error: No Git Server found
after putting in my github credentials

[liuxiaopiao]

met the same issue with provider kubernetes