It should be a container from image hortonworks/cloudbreak-web:1.2.3 named cbreak_uluwatu_1.
Can you see it with docker ps -a as terminated? If yes can you send me the logs, or try to restart it with docker restart cbreak_uluwatu_1?
Sorry to bother you again but I have a new issue related to the post. Cloudbreak api is running. It returns json as expected but I can't access the api with the UI.
It seems there is something missing again.
Can you check the developers console in your browser and see if there is a JS error there?
There was a bug in that version of cloudbreak that caused this sometimes on first page load but it ususally loads successfully after a few page refreshes.
This bug was fixed later, but there is no official release that contains it yet. If this error doesn't disappear, you can try to update the cloudbreak-web container with a patch like this:
Add this line to your cbd Profile:
and run these commands to regenerate the yml files and restart cbd:
cbd kill cbd regenerate cbd start
This will pull the latest rc container of the UI where this bug is fixed and will restart all the components. (You may need to stop your dev cloudbreak and run the local-dev command again)
Please check the logs of your UI container with
docker logs cbreak_uluwatu_1
And please also send me the cloudbreak logs in email to msereg at hortonworks com.
I'm not sure about this issue but maybe we can setup a webex tomorrow, it would be simpler I think.