Everything else is handled by other parts of the ecosystem already, image registries both private and public, orchestration, etc.
Everything else is handled by other parts of the ecosystem already, image registries both private and public, orchestration, etc.
Good move by Docker, financially speaking. They have little to lose.
A whole bunch of scenarios die now.
A lot of macOS developers imo seem to have more knowledge in their specific domain and less in how to wire up a VM to look seamless, they'll need the docker CLI to work with the local filesystem to keep a lot of existing Makefiles functional, I see a bunch of companies caughing up money in the short term just for that.
Docker Desktop on Windows itself proves quite well that WSL2 works fine for this use case.
Why would I go out of my way to set up Docker differently on my dev machine compared to my servers? That seems like a recipe for failure.