Member since
09-11-2015
3
Posts
2
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
925 | 05-30-2016 12:48 PM | |
1707 | 10-19-2015 12:48 PM |
05-30-2016
12:48 PM
seems like the deployer host has name resolution issues. it has "no internet access". from cbd docktror output:
- it cant resolve dns names (for example github.com)
- it can'y even reach google's dns server (8.8.8.8)
Can you please make sure, that you start the cbd deployer instance in a network where you have internet access?
It will be needed by ambari for yum installs
... View more
10-19-2015
12:48 PM
2 Kudos
127.0.0.1 is not gonna work for PUBLIC_IP. Please use `cbd init` to generate the initial Profile. Which will figure out the correct boot2docker ip. So this is what you should have in your Profile: export PUBLIC_IP=192.168.59.103
The output of `boot2docker ip` is **192.168.59.103** unless you have a non-standard boo2docker. So use this for PUBLIC_IP, (PRIVATE_IP can be removed from Profile After changing the Profile, configuration files has to be generated again: cbd regenerate
Now you can restart the containers: cbd start After a couple of minutes you can open the browser and log in, url and credential can be displayed: cbd login
... View more