Adding the building-bits_from_ci_container.png to the CLI instructions

.vs/VSWorkspaceState.json

@@ -1,8 +1,7 @@
 {
   "ExpandedNodes": [
-    "",
-    "\\img"
+    ""
   ],
-  "SelectedNode": "\\img\\Bower_and_Gulp_setup.png",
+  "SelectedNode": "\\06.-Setting-the-Web-SPA-application-up.md",
   "PreviewInSolutionExplorer": false
 }

03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md

@@ -23,7 +23,12 @@ By default, use the MASTER branch which supports .CSPROJ projects and .NET Core
 ### Approach building bits from a container instead of the local dev-machine
 The recommended approach is to build the .NET bits and Docker images by using an special build container/image that should be used either from the CLI or your CI/CD pipeline. Doing that way you'll make sure that what you run and test locally is also built the same way by your CI/CD pipleine (having the same dependencies available within the build container, etc.).
 
-The build container to use is based on the `image: microsoft/aspnetcore-build:1.0-1.1` ASP.NET Core build image which includes the .NET SDK, NPM and many other Web and ASP.NET dependencies (Gulp, Bower, etc.) to build your services and web apps.
+
+<img src="img/building-bits_from_ci_container.png">
+
+<p>
+
+The build container to use is based on the `image: microsoft/aspnetcore-build` ASP.NET Core build image which includes the .NET SDK, NPM and many other Web and ASP.NET dependencies (Gulp, Bower, etc.) to build your services and web apps.
 See building procedure below.