A big part of the problem is Docker the company working so hard to hide much of Docker-on-Windows behind the GUI mentioned in the article. For instance, it's easy to think of switching to WSL2 as something of a non-change when it's just a switch in the GUI. But, of course, it really means running Docker in a Hyper-V container and that means when it writes to disk, it's writing to the VM's disk.
IMHO, the GUI and the Windows Docker implementation need to do a little more (redirect files but not bog down the host) or do a lot less (force us all to understand the compromises).
The GUI really "dumbs down" Docker. At first I was pleased to see a GUI instead of the CLI. But after a few hours working with the Linux Docker's CLI I'm actually pretty comfortable with it and I can use all of it's functionality.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
A big part of the problem is Docker the company working so hard to hide much of Docker-on-Windows behind the GUI mentioned in the article. For instance, it's easy to think of switching to WSL2 as something of a non-change when it's just a switch in the GUI. But, of course, it really means running Docker in a Hyper-V container and that means when it writes to disk, it's writing to the VM's disk.
IMHO, the GUI and the Windows Docker implementation need to do a little more (redirect files but not bog down the host) or do a lot less (force us all to understand the compromises).
The GUI really "dumbs down" Docker. At first I was pleased to see a GUI instead of the CLI. But after a few hours working with the Linux Docker's CLI I'm actually pretty comfortable with it and I can use all of it's functionality.