From 989b4f2fce8eade0fbb61546cea24e42dc7772d3 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 2 Jan 2018 17:59:32 -0800 Subject: [PATCH] Updated 03. Setting the eShopOnContainers solution up in a Windows CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown) --- ...ws-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md b/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md index a07c245..d89ca89 100644 --- a/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md +++ b/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md @@ -59,8 +59,8 @@ Once Docker for Windows is installed in your machine, enter into its Settings an -### Share drives in Docker settings -This step is optional but recommended, as Docker needs sometime to access the shared drives when building, depending on the actions. +### Share drives in Docker settings (OPTIONAL) +This step is optional but recommended, as Docker sometimes needs to access the shared drives when building, depending on the actions. With the by default eShopOnContainers build process you don't need it, but if you were running a CI build container or Visual Studio, you might need it. The drive you'll need to share depends on where you place your source code.