Tell us about your request
With the recent removal of DockerCLI.exe, there doesn't appear to be a way in Docker Desktop for Windows to be able to switch between Windows and Linux container engines/daemons from the CLI. Please add one.
Which service(s) is this request for?
Docker Desktop for Windows
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I build and test and sometimes run Windows and Linux containers on my Windows laptop and frequently switch between Windows and Linux containers. I have some workflows scripted for build-and-test and the removal of DockerCLI.exe breaks my automation requiring me to manually intervene several times in the middle of scripts that used to be fully automated.
Are you currently working around the issue?
Yes, manual intervention to click on the systray icon and switch engines which costs me a lot of time and prevents me from fully automating what was previously automated and working before the removal of DockerCLI.exe
Additional context
Perhaps I missed it, but I feel that the removal of DockerCLI.exe was rather sudden and poorly communicated and handled. Many devs and testers in the community relied on this tool and its surreptitious removal has cost them much time and frustration.
The removal of the dockercli.exe tool completely killed a good portion of the automation in my build and release pipeline. PLEASE GIVE BACK THE ABILITY THAT YOU JUST RANDOMLY TOOK AWAY.
Tell us about your request With the recent removal of DockerCLI.exe, there doesn't appear to be a way in Docker Desktop for Windows to be able to switch between Windows and Linux container engines/daemons from the CLI. Please add one.
Which service(s) is this request for? Docker Desktop for Windows
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I build and test and sometimes run Windows and Linux containers on my Windows laptop and frequently switch between Windows and Linux containers. I have some workflows scripted for build-and-test and the removal of DockerCLI.exe breaks my automation requiring me to manually intervene several times in the middle of scripts that used to be fully automated.
Are you currently working around the issue? Yes, manual intervention to click on the systray icon and switch engines which costs me a lot of time and prevents me from fully automating what was previously automated and working before the removal of DockerCLI.exe
Additional context Perhaps I missed it, but I feel that the removal of DockerCLI.exe was rather sudden and poorly communicated and handled. Many devs and testers in the community relied on this tool and its surreptitious removal has cost them much time and frustration.