rawlingsj
commented
10 years ago I originally committed the example without much testing as I needed to move on from this. I suspect it's down to setting the right environment variables somehow in the JSON that's sent to Kubernetes to then be passed to the docker container so that fabric8 starts up in the desired state.
My guess is we want to set the variables below. I'll have a look later today to work out how this is done and see if it solves the issue.
export FABRIC8_ENSEMBLE_AUTO_START=true export FABRIC8_GLOBAL_RESOLVER=localip
Hi,
I have followed the README for the Kubernetes under vagrant on a mac and I couldn't access the hawtio web page. The reason was that I needed to run VirtualBox on the Mac , select the Minion-1 VM and change through the Settings icon the Network configuration from NAT to BridgedAdapter. Once I had made this change I could see the Hawtio web site from my mac's browser.
A comment in the README about this may help others experimenting.
OK, this only helped me a little. I needed to switch back to NAT to then use vagrant ssh. However, the big issue I have is that I don't seem to have a fabric as the runtime tab is not present?
[vagrant@kubernetes-minion-1 ~]$ sudo docker logs 394a7a9ad7ec Welcome to fabric8: http://fabric8.io/
Starting Fabric8 container: root Connecting to ZooKeeper: using environment: Using bindaddress: 0.0.0.0 Redirecting to /bin/systemctl start sshd.service Failed to get D-Bus connection: No connection to service manager.