Minikube setup doesn't work in China due to firewall

[alvinwo]

When I'm going to create a nodejs environment with tutorial, I get stuck.

fission env create --name nodejs --image fission/node-env

There is no response with my terminal. I'm using fission on Mac.

[soamvasani]

Did you set $FISSION_URL? Does fission env list work?

[alvinwo]

Yes, I've set $FISSION_URL

Also, I cannot get any response with 'fission env list'.
Minikube has been started already. Is there anything wrong with my operations?

[soamvasani]

Sorry you're having trouble with this. Can you check the status of the fission services and pods?

kubectl --namespace fission get services
kubectl --namespace fission get pods

Also, can you post the output of kubectl --namespace fission logs controller-xxx-yyy | tail -50 where controller-xxx-yyy is the name of the controller pod from the previous command?

BTW, if you want quicker help feel free to drop into the slack channel, http://slack.fission.io/

[alvinwo]

hi, here is the results for these commands

I cannot get logs from the controller.

[soamvasani]

We spoke on slack, and found that gcr.io is blocked in China, and so the pause container image can't be pulled, so the pods never come up.

I don't know if there's a good workaround. There's a github issue kubernetes/minikube#473, but I can't find instructions on exactly how to get around this.

[soamvasani]

If you can reach docker hub, try destroying your minikube setup with minikube delete, and then try minikube start --extra-config=kubelet.PodInfraContainerImage=kubernetes/pause.

[soamvasani]

Going to close this, the only useful thing we could do in fission is improve the error; filed issue #78 for that. @AaronWo please reach out on slack if you still need any help with setup.