@Bill Brooks Hello, if this is still an issue at this time, could you please pastebin the logs from /var/log/ambari-server? ... View more

@Ian Shrum Try connecting via SSH to the host machine ( ssh root@localhost -p2122 root/hadoop ) and then running docker ps to check if the docker container has been started. If so, from there login to the docker container ( ssh root@localhost -p2222 root/hadoop ) and run a ps ax command to check what processes are started. It's very strange that not even shellinabox is started ( port 4200 ), we haven't seen this behavior before. ... View more

@Arun Kumar M Why did you change your networking settings for it? By default it's set to NAT: ... View more

@Arun Kumar M Please explain what the issue is in more detail, from your screenshots the only thing I see is you've set your machine to a host-only network. ... View more

@pankaj kushwaha Making sure all the services are stopped and then doing a shutdown command from inside the host VM is your best bet at making sure nothing gets broken. ... View more

@Jonathan T The virtualbox and vmware versions of the sandbox are simply instances of virtualbox and vmware machines with the image pre-loaded onto them so if someone isn't accustomed to running scripts and/or installing docker on their machines they don't need to. Also docker so far isn't very OS friendly in that different distros present different bugs depending on flavors and kernel versions so downloading the vbox/vmware versions ensure that you're running it in an environment that was pre-screened to work accordingly. Regarding the behavior you are experiencing I can't really form on opinion by just the output you submitted but if I were to guess it would probably be a docker-related issue and perhaps your docker/ambari logs will provide more insight. Is everything else running alright now that you managed to bring it up? ... View more

@pankaj kushwaha hello, did your instance get terminated while running? To me your error looks like an FS issue and we've had a couple more instances where the overlayFS that docker uses got corrupted by incorrect shutdowns. If that's the case your best bet is re-importing the sandbox. ... View more

@Jonathan T from what I understand you are trying to run the docker image of sandbox natively correct? In that case, what OS are you running on your machine. I'm asking because if it's ubuntu the problem you're probably running into is the fact that apparmor is blocking critical services of the sandbox container. ... View more

@Prasanna G Hello, there has been another case with a similar issue under similar circumstances and the issue here seems to be that killing the docker process abruptly creates issues on the FS level. Now that's bad news because these aren't straightforward to debug. You need to try and start the docker container with strace, find the actual system call that's failing and go from there. Alternatively, much easier and probably faster is to re-import the sandbox. ... View more

I don't think it's necessarily the right OS version, but configuring AppArmor so that they work together. I did attempt to but didn't have the time and gave up after about 2 hours and just started developing on centos which works from the get-go. ... View more