Skip to content
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

Trying to run up binder with minikube #1

Open
Analect opened this issue Nov 8, 2016 · 0 comments
Open

Trying to run up binder with minikube #1

Analect opened this issue Nov 8, 2016 · 0 comments

Comments

@Analect
Copy link

Analect commented Nov 8, 2016

@andrewosh
I stumbled upon this script ... and was trying to run up the latest binder locally on a mac with a running minikube, but somehow it's not cooperating.

Simultaneously, I was trying to work through http://docs.mybinder.org/custom-deployments .. specifically the 'local deployments' section although there's nothing in there specifically referencing minikube.

I tried running binder-control start-all below and input vagrant when asked which provider, thinking that might be the right option to pick up a running minikube cluster ... but that failed.

$> binder-control start-all
prompt: Would you like to launch a Kubernetes cluster?:  (yes) yes
prompt: Would you like to launch Kubernetes locally with Docker? (local testing only)?:  (no) yes
prompt: Would you like to launch the database service?:  (yes) yes
prompt: Would you like to launch the logging service?:  (yes) yes
Starting 'start' - kube-cluster
prompt: How many minion nodes would you like in your cluster?:  (1) 3
prompt: What cloud provider would you like to use?:  (gce) vagrant
/Users/me/.nvm/versions/node/v6.2.1/lib/node_modules/binder-control/services/kube-cluster/start-kubernetes.sh: line 4: wget: command not found
tar: Error opening archive: Failed to open 'kubernetes.tar.gz'
rm: kubernetes.tar.gz: No such file or directory
KUBE_DIR:  /Users/me/.nvm/versions/node/v6.2.1/lib/node_modules/binder-control/services/kube-cluster/kubernetes
/Users/me/.nvm/versions/node/v6.2.1/lib/node_modules/binder-control/services/kube-cluster/start-kubernetes.sh: line 10: /Users/me/.nvm/versions/node/v6.2.1/lib/node_modules/binder-control/services/kube-cluster/kubernetes/cluster/kube-up.sh: No such file or directory
{ msg: 'script not found : /Users/me/.nvm/versions/node/v6.2.1/lib/node_modules/binder-control/services/kube-cluster/kubernetes/cluster/kubectl.sh' }
Finished 'start' - kube-cluster
Failed to start service kube-cluster: Error: error starting kubernetes cluster: [object Object]
Starting 'start' - kube-vm
Finished 'start' - kube-vm
Started service kube-vm successfully
Starting 'start' - db
Finished 'start' - db
Started service db successfully
Starting 'start' - logging
Waiting 2 minutes for logging containers to start up...
^C
$ Starting the binder-build server...
Starting the binder-deploy-kubernetes server...
Starting the binder-web server...
Starting the binder-health-checker server...
Pulling all base images...
Using default tag: latest

Any pointers on how I might get this working?

Also, it seems the docker binder-base image weighs in at almost 5GB. I can't seem to locate the github repo that underlies that ... any reason why this image is so huge? Thanks. Colum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant