Whenever I’m pulling containers from “hub.docker.com” for eg:- “docker pull node” or"docker pull selenium/node-chrome"or “docker pull selenium/node-firefox” etc,
I always get “latest: Pulling from library/node
image operating system “linux” cannot be used on this platform” error.
Note: I have already selected “Switch to Windows Containers” present at the bottom of the window screen
Please find my docker version below and info:
PS C:\WINDOWS\system32> docker version
Client:
Version: 1.13.1
API version: 1.26
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: windows/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.24)
Go version: go1.7.5
Git commit: 092cba3
Built: Wed Feb 8 08:47:51 2017
OS/Arch: windows/amd64
Experimental: true
when you have docker for windows installed on win10 if has 1 modes. windows container mode and linux container mode.
you need to right click and switch to linux containers before you pull your selenium images.
Thank you for your reply!
If you see my Docker Info above, you will see that I have already selected “Windows container mode”. If you have tried pulling selenium hub or chrome image in your system and if its working, then please let me know further how you achieved it.
For me its working on Linux container mode and not Windows container mode.
May be we have to create our own Selenium container which can work on Windows mode. And I’m totally unaware of how to create Selenium image for windows.
Is there an update to Windows 10 Pro beyond ver 1803 and build 17134.165? Cos’ I have this and switching to LCoW says my windows version is not compatible.
I will try this. In the mean time, switching to “LCoW” on Windows pops up a message saying my windows version is not compatible. Will this “pull” fix this issue?
Docker crashed when I tried to switch to Linux Containers… It is blocking me, what is the resolution?
Unable to stop - The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Service ‘Hyper-V Host Compute Service (vmcompute)’ cannot be started due to the following error: Cannot start service vmcompute on computer ‘.’.
at Docker.Core.Pipe.NamedPipeClient.d__5.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object parameters)
at Docker.Actions.<>c__DisplayClass36_0.b__0()
at Docker.ApiServices.TaskQueuing.TaskQueue.<>c__DisplayClass17_0.<.ctor>b__1()
For the sake of readers finding this in the future (as it’s the first google result for the error in the original post), note that you CAN in fact get Docker Desktop on Windows to permit you to pull or run a Linux container while in Windows Container mode. You need to switch to “experimental mode” in Docker Desktop (done in its settings).
Some will wonder, “why would you want to”, and it’s that this also allows one to run both Windows and Linux containers at once, including within Docker Compose. Perhaps someone wants to front a Linux-based Tomcat container with IIS, or wants to have an ASP.NET app talk to a Linux-based Redis cache.
The point is: if one WANTS to run a Linux container while in Windows container mode, one CAN. But again it is EXPERIMENTAL, and surely some will speak up with reasons they think this is a “crazy idea” for Docker to “even allow it”.
