From c9844a006f6302baeed6236b5e3d746f705a6ecb Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 2 May 2017 12:42:18 -0700 Subject: [PATCH] Updated 02. Setting eShopOnContainer solution up in a Visual Studio 2017 environment (markdown) --- ...Container-solution-up-in-a-Visual-Studio-2017-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md index fc48c5b..5102fd8 100644 --- a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md +++ b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md @@ -61,7 +61,7 @@ The drive you'll need to share depends on where you place your source code. -NOTE: If you are using Windows 10 Creators Update (Windows 10 Creators Update, version 1703, codenamed "Redstone 2") and your machine is joined to a Windows or Azure Domain, you might get some issues when configuring the share drives for Docker. Providing a local user credential (from your actual machine) instead of a Windows/Azure Domain user credential might solve the issue. +**NOTE**: If you are using **Windows 10 Creators Update** (Windows 10 Creators Update, version 1703, codenamed "Redstone 2") **and your machine is joined to a Windows or Azure Domain**, you might get some issues when configuring the share drives for Docker. Providing a local user credential (from your actual machine) instead of a Windows/Azure Domain user credential might solve the issue. Check the following blog post for additional workarounds: https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-windows-volumes/