Closed hahla closed 10 years ago
Hi,
Can you please re-run the install scripts (based on the blog posts) - you should use the sequenceiq/ambari:1.6.0 tag instead of the latest tags (the master contains the latest snapshot).
If you'd like to access the Ambari UI from the host you should set up the routing: sudo route add -net 172.17.0.0/16 192.168.59.103
Janos
Thank you for the fast reply!
I have done the following just now after cleaning out the previous images and stop/start boot2docker.
The single-node blog entry does not have an entry for the repo tag, so I assume you are referring to the multi-node instance blog entry? Here is what I just have done:
docker pull sequenceiq/ambari:1.6.0 curl -Lo .amb j.mp/docker-ambari && . .amb && amb-deploy-cluster (I checked the script downloaded from curl uses "sequenceiq/ambari:1.6.0" tag as expected. i.e. in ambari-functions: : ${IMAGE:="sequenceiq/ambari:1.6.0"}
After the installation runs and is completed, it dumps me back to host bash and it looks like it's running.
docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES cffac93e1e81 sequenceiq/ambari:1.6.0 "/usr/local/serf/bin 19 minutes ago Up 19 minutes 7946/tcp, 8080/tcp, 7373/tcp amb2 f6a716e37d82 sequenceiq/ambari:1.6.0 "/usr/local/serf/bin 19 minutes ago Up 19 minutes 7373/tcp, 7946/tcp, 8080/tcp amb1 bdc1efc66b3f sequenceiq/ambari:1.6.0 "/usr/local/serf/bin 19 minutes ago Up 19 minutes 7373/tcp, 7946/tcp, 8080/tcp amb0
Then I modified the command from the single-node blog post to get the IP address for the 1st container server with: docker inspect -f "" amb0
... but the container IP given just hangs on connect from the host, i.e. http://172.17.0.2:8080
Note: I'm not running any funny firewall software.
docker attach bdc1efc66b3f # this hangs also, whereas I was hoping to get a shell to debug the ambari server from within the container
Is routing configured from the host into the container (sudo route add -net 172.17.0.0/16 192.168.59.103)?
Also can you please let me know the b2b and docker versions?
Ah yes, it was routing! Great work.
docker -v Docker version 1.2.0, build fa7b24f
boot2docker version Client version: v1.2.0 Git commit: a551732
This is a really neat project and I'm looking forward to seeing it running, unfortunately I've hit a snag testing it on Mavericks, and I cannot connect to the ambari server.
Here are the steps I am doing:
Also a few docker command outputs for your reference:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6e5fa0735dfd sequenceiq/ambari:latest "/usr/local/serf/bin 39 minutes ago Up 17 minutes 7373/tcp, 7946/tcp, 0.0.0.0:49153->8080/tcp ambari-singlenode