# Using Docker on Windows with Virtual Box

**URL:** <https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358>\
**Category:** General Discussion\
**Created:** [December 9, 2020, 9:27pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358 "2020-12-09T21:27:48Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 9, 2020, 9:27pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/1 "2020-12-09T21:27:49Z")

</div>

I would like to start exploring Docker but unfortunately I use Virtual Box for other development purposes. What are my options to run Docker and Virtual Box **without** having to use Hyper-V which made Virtual Box totally useless.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 9, 2020, 9:31pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/2 "2020-12-09T21:31:32Z")

</div>

[This](https://docs.docker.com/docker-for-windows/) seems to mention something about “WSL2 Mode” as opposed to “Hyper-V Mode”, which reduces some of the configuration options available to you but sounds like it might still work.

Alternatively you could just spin up an Ubuntu VM in Virtual Box and then use Docker inside the VM?

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 9, 2020, 9:33pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/3 "2020-12-09T21:33:20Z")

</div>

Yes. I just tried WSL2 Mode which still uses Hyper-V somehow? It is not clear but it seems to have made Virtual Box fall back to Hyper-V which is no good.

I’m leaning toward the second option but how much more complicated would it be to run Docker inside of a virtual machine?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [December 9, 2020, 9:34pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/4 "2020-12-09T21:34:07Z")

</div>

Running it in a VM is probably your best option. From what I’ve heard the experience on Windows is pretty bad anyway.

---

<div class="post-metadata">

**Author:** ![chasondeshotel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/chasondeshotel/32/20032_2.png) [@chasondeshotel](https://forum.inductiveautomation.com/u/chasondeshotel)\
**Post date:** [December 10, 2020, 4:35pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/5 "2020-12-10T16:35:15Z")

</div>

> [@Kevin.Herron](#):
>
> the experience on Windows is pretty bad

This is true of the entire OS

> I just tried WSL2 Mode which still uses Hyper-V somehow?

Have you tried disabling Hyper-V entirely?

> **[How to Disable Hyper-V Completely in Windows 10 - Petri IT Knowledgebase](https://petri.com/how-to-disable-hyper-v-completely-in-windows-10)**
>
> Hyper-V is an optional feature in Windows 10 that can be used to run virtual machines (VMs) and perform other virtualization duties, such as supporting Credential Guard and Windows Sandbox. Like all Windows 10 features, you can add or remove Hyper-V...

Is your copy of VirtualBox up to date? I think they've been doing core changes recently and I've had a couple updates that didn't work on my machine

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [December 10, 2020, 5:56pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/6 "2020-12-10T17:56:01Z")

</div>

@brandon1, what version of Windows are you running? There have been some major improvements starting with Windows 10 2004 that make running other hypervisors alongside Hyper-V an option. Also, you’d want to be on Windows 10 2004 at a minimum for WSL2 support, which makes Docker Desktop _muuuuch_ better on Windows…

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 10, 2020, 7:04pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/7 "2020-12-10T19:04:30Z")

</div>

I am running 2004 or newer. Not by my computer at the moment. When I had wsl2 running it told my virtual box was using Hyper-V. Can you point me to a resource that tells me how to run virtual boxes hypervisor along with wsl2?

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 10, 2020, 7:05pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/8 "2020-12-10T19:05:10Z")

</div>

> [@chasondeshotel](#):
>
> Is your copy of VirtualBox up to date?

I'm running 6.1.x

---

<div class="post-metadata">

**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\
**Post date:** [December 11, 2020, 4:02am UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/9 "2020-12-11T04:02:02Z")

</div>

@brandon1, on my Windows dev box here at home I was able to verify ability to run VMware Workstation, VirtualBox, and Docker under WSL2 simultaneously:

 ![2020-12-10 at 9.58 PM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/9/89f888d1f3ca445714692496dcac280076ee3c6a.jpeg)

I’d recommend you check the System-\>Advanced tab and try adjusting the Paravirtualization interface. Under VirtualBox 6.1.16, the machine I was running (spooled up via Vagrant, fwiw) was set with `Default`:

![2020-12-10 at 9.59 PM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/3/233eece01a8f59f3f0535abb95048fa21a703123.png)

EDIT: This was all working under Windows 10 2004… Updated to 20H2 and everything is still purring along…

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [December 11, 2020, 1:05pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/10 "2020-12-11T13:05:42Z")

</div>

Thank you Kevin. When I get time I will try again. I followed a tutorial online and must have not realized I could disable Hyper-V and still run WSL2.

I appreciate the help and I will report back. Happy Friday!

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [December 11, 2020, 3:14pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/11 "2020-12-11T15:14:13Z")

</div>

+1 for WSL2.  
I’ve been running VMWare Workstation and Docker under WSL2 side-by-side on 20H2 without issues.

---

<div class="post-metadata">

**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\
**Post date:** [December 18, 2020, 9:31pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/12 "2020-12-18T21:31:45Z")

</div>

I’ve been attempting to use Ignition on Docker on WSL2 for a couple days. Everything seems to work fine except launching the designer or a client.

Port 8081 is mapped to 8088 in the container. From a web browser in windows (on the host machine), the gateway web page is reachable with [http://localhost:8081](http://localhost:8081). Gateway backups have been successfully imported and projects, database connections, etc. are all visible. Database connections are all valid, so I know the container can see SQL Server on the host computer.

When launching the designer I have tried connecting to [http://localhost:8081](http://localhost:8081), [http://0.0.0.0:8081](http://0.0.0.0:8081), and [http://127.0.0.1:8081](http://127.0.0.1:8081). The response is always that the host is unreachable.

Any suggestions?

Thanks,  
Mack

---

<div class="post-metadata">

**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\
**Post date:** [December 18, 2020, 9:45pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/13 "2020-12-18T21:45:55Z")

</div>

@kcollins, Do you know if you run HyperV and VMWare alongside? I recall reading that it was going to be available, but last time I tried it didn’t work for me.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 18, 2020, 10:04pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/14 "2020-12-18T22:04:57Z")

</div>

> [@mcgheeiv](#):
>
> Any suggestions?

Did you manually configure the public HTTP address settings?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/3/33f8c4176576ffeba92db89c10c4d361b18a5c48.png)  
You probably need to ensure that this block is set up to tell clients/designers to use the remapped port; from Ignition's perspective inside the container, 8088 is correct.

---

<div class="post-metadata">

**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\
**Post date:** [December 18, 2020, 10:19pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/15 "2020-12-18T22:19:29Z")

</div>

Gregg, yes, with Workstation 16 you can run VMs under there alongside VMs running under HyperV!

---

<div class="post-metadata">

**Author:** ![mcgheeiv](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@mcgheeiv](https://forum.inductiveautomation.com/u/mcgheeiv)\
**Post date:** [December 18, 2020, 10:47pm UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/16 "2020-12-18T22:47:38Z")

</div>

I created another container that maps 8088 to 8088, same issue. I can get to the gateway web page but not the designer.

---

<div class="post-metadata">

**Author:** ![GreggCavazos](https://avatars.discourse-cdn.com/v4/letter/g/90db22/32.png) [@GreggCavazos](https://forum.inductiveautomation.com/u/GreggCavazos)\
**Post date:** [December 21, 2020, 2:57am UTC](https://forum.inductiveautomation.com/t/using-docker-on-windows-with-virtual-box/41358/17 "2020-12-21T02:57:30Z")

</div>

> [@Kevin.Collins](#):
>
> Workstation 16

that may be my problem, if I am not mistaken its been a little bit more than a year since I upgraded to Workstation 15, I've been getting the notifications to upgrade, but I was wondering if I should or not, maybe I just found a reason to pull the trigger.
