I had that some time, I always booted into the wrong one.
Also at least Docker4Windows (that one using Hyper-V) was set to use a single GiB of RAM on a system with 8 GiB physical. Even directly after boot, I had to try several times before I was able to start without getting OOM. VBox based docker just works, using a max of 4 GiB, consuming near to nothing after starting docker-machine and only as much as necessary when a container was running. Hyper-V based Docker sits on its single GiB, not releasing the tiniest bit when no containers are running (but not consuming more if they are running). And a single GiB of RAM is far too less for most things.
