search

amplab / docker-scripts

Dockerfiles and scripts for Spark and Shark Docker images
261 stars 102 forks source link

Docker worker install runs forever 'waiting for workers to register ............................' #42

Closed amitoj closed 10 years ago

amitoj commented 10 years ago

This issue has been previously raised and closed by dbaba https://github.com/amplab/docker-scripts/issues/39

But the suggested solution is not working for me.

Following the example explained in https://amplab.cs.berkeley.edu/2013/10/23/got-a-minute-spin-up-a-spark-cluster-on-your-laptop-with-docker/

I've tried so far,

sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:1.0.0 -c sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:0.8.0 -c sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:1.0.0 sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:0.8.0 sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:1.0.0 -w 3

My output is

[vagrant@docker ~]$ sudo ./docker-scripts/deploy/deploy.sh -i amplab/spark:1.0.0 -w 3 * Starting Spark 1.0.0 * starting nameserver container started nameserver container: ee09901077c4c1a61e3cdb4d79b30060de777abae4c9fd0580b2176a2aa4f58a DNS host->IP file mapped: /tmp/dnsdir_28254/0hosts NAMESERVER_IP: 172.17.0.20 waiting for nameserver to come up starting master container started master container: 723fafc1b39de3fe6a28130968b4d65e8adf78ea131176621203f362a689ab8e MASTER_IP: 172.17.0.21 waiting for master ................ waiting for nameserver to find master starting worker container started worker container: 3a061e3091fe435f18673c29c586e58e024011620f7864fd55191cbad23001d5 starting worker container started worker container: 1c2be21cc224942f4d26efacc9b0d09ed900affaee1bdafff0bf9a2ddf54b4c3 starting worker container started worker container: 65bc96a8777e1e68dcece7bf73dfcf09b4a2d64bb2372a9ce0916ed99fc52692 waiting for workers to register .......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Is there a way to check the installation log of these containers?

amitoj commented 10 years ago

Deleted all and re-created the boot2docker environment. Seems to be working now.