Is it possible to dockerize Internet Explorer?

Question

I want to run multiple Internet Explorer versions on the same machine using Selenium WebDriver with Docker instead of Virtual Machines. Docker runs on entirely Linux, as fa

Answer 1

You can install wine, and IE6 or IE7. I guess you would prefer IE 10 or IE11.

Have a look for example at

https://hub.docker.com/r/tianon/wine/

or

https://hub.docker.com/r/jess/wine/,

and according to winehq.org, you can use an outdated browser such as IE7, if you modify the previous Dockerfiles.

Do not forget you will not have all the DLL available with wine.

Answer 2

Still there is no official approach to run IE/EDGE inside docker as "No Windows docker images have GUI, so we cannot test IE11, EDGE."

But,We can install virtual-box and make this happen.

This approach adds extra layer of virtualization[Nesting of virtualization] on the top of docker to make the IE/Edge execution happen and I think in near future it may leads to to performance issue for heavy testing.

If Selenium testing is what you are looking for and don't have heavy load , you can give a try to the approach mentioned in the link.

Youtube - Selenium Windows containers in Docker under Linux

Github - Windows Images

Blogpost - selenium-on-windows-docker-revolution

Answer 3

IE 6/7/8 with selenium server could be used on docker using this image: https://github.com/sormy/docker-oldie

Answer 4

Docker does not currently work with Windows based applications. The Docker on Azure is Docker running on Linux VM's in Azure. With the advent of Docker for Windows you would think it would be possible, however IE/Edge does not support headless mode. Microsoft has announced that Edge is switching to chromium which will hopefully, finally, bring headless mode to IE/Edge. Docker will never support a GUI environment, it runs counter to their mission.

Answer 5

Microsoft have released a new feature called Windows Sandbox as part of Windows 10 1903. I believe that it is designed to fill this specific gap, and does allow for some setup to be done prior to the Sandbox being started up. I'm currently looking into seeing if we can use this approach for our own Selenium testing, but I encourage others to check it out too.