Updated 04. Setting eShopOnContainer solution up in a Mac, VS for Mac or with CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown)

04.-Setting-eShopOnContainer-solution-up-in-a-Mac,-VS-for-Mac-or-with-CLI-environment--(dotnet-CLI,-Docker-CLI-and-VS-Code).md

@@ -108,6 +108,22 @@ And by typing `docker ps` you can see the containers running in Docker. The infr
 
 This is the simplest way to do it from the CLI, but until a [bug is solved in .NET CLI when running "dotnet publish" within a container](https://github.com/Microsoft/msbuild/issues/2153#issuecomment-305375162), please, follow the OPTION B.2 explained below, which is building the app's .NET binaries in the local Mac, instead of from a Linux build-container.
 
+
+---
+
+*IMPORTANT NOTE (as of Oct. 2017):*
+ 
+This is the simplest way to do it from the CLI, but if you get the following error when compiling from the Linux build-container:
+
+`MSBUILD : error MSB4017: The build stopped unexpectedly because of an unexpected logger failure.`
+`ci-build_1  | Microsoft.Build.Exceptions.InternalLoggerException: The build stopped unexpectedly because of an unexpected logger failure. ---> System.IO.IOException: The process cannot access the file because it is being used by another process.`
+
+That is a [bug in .NET CLI when running "dotnet publish" within a container](https://github.com/Microsoft/msbuild/issues/2153#issuecomment-305375162).
+
+If you get this issue, until the fix is released by the dotnet CLI team in the next version of the .NET CLI, in the meantime, follow the OPTION B.2 explained below, which is building the app's .NET binaries in the local Mac, instead of from a Linux build-container. 
+
+---
+
 Open a bash shell and run the following four commands:
 
 ```