I am also facing the same problem. But I soved it by deleting the virtual box logs which is located at
c:/users/' your pcname'/.VirtualBox (for windows users only)
Delete only those files which have names like 'VBoxSVC.log' .Remember to do this step only when your virtualbox is closed.
I tried to start the sandbox (HDP 2.6, 8 GB assigned) on a Core i7 with 16 GB RAM. Booting is not finished after more than 30 hours (CPU is very busy). Free RAM is available, according to the task manager VirtualBox is using about 124 MB of RAM only. Is there anything I could do?
I am running HDP version 2.6.1 on VMware.
Initially it starts up fine, but any of my attempts to shutdown the "docker" container for the sandox gracefully failed, and just shutting down the host VM via the VMware Player window resulted in the SandboxContainer startup hanging at the next startup.
Sending shutdown commands to the docker OS (NOT to the host VM OS) via SSH does not work because of some permission issues.
I ended up starting up the VM initially and never shutting it down, only suspending. Will stick with this workaround until I stumble upon a way to shutdown the sandbox containter gracefully and only THEN shutting down the host VM.
I miss the days when the sandbox was running on just a plain VM instead of this VM+docker combo. You can't even see what happens when the docker is being started...
Same problem here. I am running the HDP sandbox 2.6.1 on VirtualBox 5.1.26 on a Centos 7 host. The VM never finishes booting. see attached screen shot. After about 10 minutes it is still starting the sandbox container (hdp1.png), and after 3 days it is stuck between cleaning up temporary directories and network manager script dispatcher (hdp2.png).
@Paul Hodor, just ignore the message and type in
@Paul Hodor just ignore the message and type in