Docker for Windows, Creators Update and Volume Sharing Linux Containers

If you're attempting to use Volume Sharing with Docker for Windows after you've installed the Creators Update, you may get errors indicating a Firewall Port must be opened.  This combination of the Creators Update, Domain Joined machines and enabling volume sharing has had a recent regression we're working to resolve.

Note: this only applies to Linux Volume Sharing. Be sure Docker for Windows is set to Linux.


Steps to re-enable volume mounting:

  1. Open Explorer, right-click on drive C and select properties
  2. Click the Sharing tab and then Advanced Sharing button
  3. Check the Share this folder, hit [OK], and then close
  4. Repeat above steps for other drives that you want shared  (I did this for C,D, and E), all my local drives in case it matters
  5. Open Control Panel\Network and Internet\Network and Sharing Center
  6. Select the vEthernet (DockerNAT) connection
  7. Click [Properties]
  8. Select File and Printer Sharing for Microsoft Networks
  9. Choose Uninstall, and [Yes] to the dialog that appears
  10.  Click [Install..]  and select “Service"
  11. Click Add.. and then select “File and Printer Sharing for Microsoft Networks”
  12. Close all the dialogs
  13. Open Docker for Windows and share the drives again

This should get you going. If not, please help us understand what's unique.

We hope to post an update here that all you need is to simply update ___ and you'll no longer need this workaround.


Comments (4)
  1. Eugen Mayer says:

    With docker for windows volume sharing can slow down the application performance significantly (50-70 times slower) then without shares. A similar problem exists with OSX and docker-for-mac – see performance lets you speed up both up to the native speed again, its available for both, OSX and now for windows:

    Give it a try, its a great companion for docker for windows and a huge productivity boost

  2. Johan Westling says:

    Did this a few days ago and then it worked for a few days. Now a weekend later I’m stuck in the same firewall blocking message. I’ve tried with and without Symantec Endpoint Protection and Windows firewall, also tried factory resetting Docker and undo, redo the steps above. Also hoping for a update real soon. 🙂

    1. Steve Lasker says:

      Hi Johan,
      We (Microsoft & Docker) are working to understand the core problem. The firewall suggestion doesn’t appear to be the answer, rather an exception caught in networking and just a generalized answer.
      What we’re learning is the configuration must be done after each reboot, or possibly a network change. From a wired to wireless for instance.
      The visual clues above can also be achieved with the following:
      Disable-NetAdapterBinding -Name “vEthernet (DockerNAT)” -ComponentID ms_server
      Enable-NetAdapterBinding -Name “vEthernet (DockerNAT)” -ComponentID ms_server
      We’re looking to automate this in a script form in Docker for Windows as a workaround until we can get a real fix.

      1. Amit says:

        Hi Steve,
        solution you have provided is not working me for at all; I tried other suggestion to make DockerNat private as well; this also hasnt helped at all. is there any better solution

Comments are closed.

Skip to main content