@Sunile Manjee Great article. I think you have a typo in your run command. You use sunileman/dockernifi in the pull, but sunileman/nifi in the run. The run command doesn't work as you have it shown. ... View more

If you only have 8GB of ram on your computer, you are going to have some real issues trying to get the Sandbox to work. The sandbox requires a minimum of 8GB of memory just for the sandbox, although it works much better with 10-12GB allocated. If you try to run the Sandbox with only 8GB total on your computer, you don't have any memory left over for Windows. ... View more

@krishnan srinivasan What version of Windows 10 do you have installed? Do you have the Hyper-V option enabled? That will interfere with VirtualBox causing VirutalBox to not work properly. Can you load other VMs in VirtualBox? ... View more

@Sebastian Hätälä Can you provide the string you are using for the JDBC interpreter? By default, the %jdbc interpreter is intended to be used with Postgres. Check your interpreter settings. You may have to use %jdbc(hive) as your interpreter string. ... View more

I'm glad to hear that! ... View more

@indrajeet gour Have you tried giving the VM more memory in VirtualBox? I tend to give mine 12GB of memory as it performs better. When you import the VM it defaults to 8GB which is the bare minimum. The first time you boot up the VM, it often takes longer than any time after that. While waiting for the console to to show the login screen, you can login the VM via ssh -p 2122 root@localhost. The default password is hadoop. You can log into the Docker sandbox that runs within that VM via ssh -p 2222 root@localhost. Again, the default password is hadoop. Once you have logged into, you can take a look at top to see if there are any processes taking up a lot of CPU resources. ... View more