Support Questions
Find answers, ask questions, and share your expertise

docker exited with 139 when running cloudera/quickstart:latest

Highlighted

Re: docker exited with 139 when running cloudera/quickstart:latest

Master Collaborator

Unfortunately I don’t have windows machine to test this out but this works flawlessly in Linux system. I am assuming kernel dump/system logs can give you guys some more insight. 
If someone have highly configured Win machine then we might isolate the memory issue if that’s the cause as suspected above. The image Ideally need 8-10GB RAM dedicated for this particular VM only. 


Cheers!
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

Re: docker exited with 139 when running cloudera/quickstart:latest

New Contributor

The WSL2 Engine is the culprit here. Revert to the non-WSL2 (Hyper-v) engine and it works.

Don't have an account?