Configuring Windows vEthernet Adapter Networks to Properly Support Docker Container Volumes

[scrap-worker]

Help us make content visible

• Searched for Docker container volumes and vEthernet
• Found "Docker containers, images, and registries"

Configuring Windows vEthernet Adapter Networks to Properly Support Docker Container Volumes

• There is no generally known way to support Docker Container Volumes in Windows when Windows Firewall is enabled. This is due in part to the fact that Windows defines the vEthernet Adapter networks as "Public". There does not appear to be a way to manually identify these virtual networks. All work-arounds (see the docker for windows issue below) expose users to potential security risks.
• This document should be available directly under "Docker containers, images, and registries."
• Abstract: There are some complexities involved with getting Windows, Windows Firewall and Docker for Windows configured to support Docker Container Volumes in a stable and secure manner.
• Outline:
  • The vEthernet adapter and how Windows identifies networks.
  • Windows Firewall Rules
    • Public Network (Deny Default / Deny All)
  • Docker for Windows and the DockerNAT (The 10.0.75.x IP space it creates)
  • Configuration Options

Further context: docker/for-win#367 (comment)

edit by @mairaw: added article details

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: aaef5307-5012-1192-2491-c6f8957e080c
• Version Independent ID: 8c5224d8-56b6-4d05-067f-21423ba787b0
• Content: Docker containers, images, and registries
• Content Source: docs/architecture/microservices/container-docker-introduction/docker-containers-images-registries.md
• Product: dotnet
• Technology: dotnet-ebooks
• GitHub Login: @nishanil
• Microsoft Alias: nanil

[mairaw]

@Thraka can you take a look at this feedback?

[mairaw]

Also adding @mvelosop and @nishanil since the feedback seems to be related to the e-book article and not our own Docker content.

[mvelosop]

Hi @CyrexCore2k, thanks for the heads up!

@mairaw, I just have a basic knowledge of networks, so I can't go too deep in this issue (if at all), however this seem to be related to a recurring issue we've been having in eShopOnContainers.

At some point @huangmaoyixxx suggested a solution to issue #295 that seems to have worked for quite some people.

However, I'm not sure the Microservices Architecture Guide is the right place to show this level of detail. Anyway I do think this would be a great topic for a page in eShopOnContainers's wiki to which we could link from the guide.

@CyrexCore2k, it looks like you are knowledable in this topic, so it'd be great if you could explain this in the wiki 😊!

[scrap-worker]

Thanks @mairaw and @mvelosop for your responses.

The solution suggested by @huangmaoyixxx appears to for a different issue and in the context of a non-corporate machine. Here is the situation that I'm in:

1. Corporate Group Policy Firewall rules are set to deny all inbound access from networks designated as Public. While I can override these settings to allow inbound connections on Public networks I would probably be violating (a justifiable) corporate security policy and exposing my machine to security risks whenever I connect to Wifi at a coffee shop or airport.
2. Windows Firewall designates all "unidentified networks" as Public.
3. Docker for Windows creates a network using the Virtual NIC and calls it DockerNAT
4. Windows Networking designates DockerNAT as an unidentified network. I have not discovered a way to identify the network.
5. When Docker containers attempt to mount volumes from the host machine an inbound connection from the Docker daemon to the host machine is made on this network.

Obviously there is little/no security risk to allowing inbound connections from DockerNAT but given these five items I have not discovered a way to permanently allow inbound connections from DockerNAT. A solution which does not survive reboots is to tell Windows Firewall to consider the DockerNAT network as Private even though it is an unidentified network using the command:

Get-NetConnectionProfile | Where-Object { $_.InterfaceAlias -match "(DockerNAT)" } | ForEach-Object { Set-NetConnectionProfile -InterfaceIndex $_.InterfaceIndex -NetworkCategory Private }

While I do agree this documentation may not be the appropriate place to dig into the details of the issue this is where I ended up after a google search. Pointing to another location makes sense and while I can see how the eShopOnContainers project has run into the same thing it seems like it too would benefit from a location where this documentation can be placed.

Question is, where, and who do we talk to about this? Not trying to assign blame or downplay the complexities involved but this appears to be a Windows issue. There should be a way that Docker for Windows can set up the DockerNAT network it creates so that Windows Networking can identify the network (and hence Windows Firewall would allow me to permanently specify it as a Private Network) but since I can't figure out how to do that as an Administrator of my own machine my (semi-educated) guess is that Windows Networking does not provide a way or document how to do this. I don't know enough about the internals of Microsoft to know how to facilitate getting the .Net Core / Windows Networking / Windows Firewall people and perhaps some knowledgeable Docker devs to coordinate and come to a solution.

@mairaw would you be able to offer some guidance here?

[Thraka]

This is outside our scope. After reading through the threads (and others on Dockers site) it sounds like the problem is with Docker and Windows not playing nicely together. This isn't related to .NET at all.

The main pain point sounds like you can't customize the network that docker installs because after reboot or upgrade docker reverts your changes. The problem seems to be with Docker not allowing that customization to persist.

It would be nice if Docker (during setup) would ask you if you want a locked down network (public-restricted) or a developer machine network (private-unrestricted) and set the defaults for the network appropriately.

If we had a tutorial that was related to a .NET Core app where we needed this network working, we would be describing the same thing: run this powershell script each time you start developing with Docker to get around the problem. Until Docker allows you to customize the default behavior of the network, we're all stuck in this situation.