ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Cesar De la Torre 2018-01-02 16:56:35 -08:00
parent 9953dabbe1
commit 290dd5e2d5
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -23,6 +23,8 @@ This CLI environment means that you want to build/run by using the CLI (Command
<p> <p>
You don't need Visual Studio 2017 for this environment but can use any code editor like Visual Studio Code, Sublime, etc. Of course, you could still use VS 2017 at the same time, as well. You don't need Visual Studio 2017 for this environment but can use any code editor like Visual Studio Code, Sublime, etc. Of course, you could still use VS 2017 at the same time, as well.
## Docker Multi-stage support
Since December 2017, Visual Studio 2017 15.5 and eShopOnContainers support [Docker Multi-stage](https://blogs.msdn.microsoft.com/stevelasker/2017/09/11/net-and-multistage-dockerfiles/), therefore, the steps in order to compile the .NET apps/projects before creating the Docker images can now be performed in a single step with "docker-compose build" or "docker build".
## Prerequisites (Software requirements) ## Prerequisites (Software requirements)
@ -33,7 +35,7 @@ You don't need Visual Studio 2017 for this environment but can use any code edit
1. [.NET Core and SDK](http://dot.net). Install the SDK and runtime. 1. [.NET Core and SDK](http://dot.net). Install the SDK and runtime.
1. Any code editor, like [Visual Studio Code](https://code.visualstudio.com/) 1. Any code editor, like [Visual Studio Code](https://code.visualstudio.com/)
*IMPORTANT NOTE:* When building with the Linux build-container (option A explained below) you don't really need to have installed Node, NPM, Bower or not even .NET Core SDK in your local Windows machine, as the Linux build-container has all the needed SDKs to compile the projects. However, we recommend to have it installed on Windows so you can do further development and testing. *IMPORTANT NOTE:* When building with Docker Multi-stage you don't really need to have installed Node, NPM, Bower or not even .NET Core SDK in your local Windows machine, as the build image used by Docker Multi-stage has all the needed SDKs to compile the projects. However, we recommend to have it installed on Windows so you can do further development and testing.
# Setting up the development environment # Setting up the development environment
@ -57,9 +59,9 @@ Once Docker for Windows is installed in your machine, enter into its Settings an
<img src="img/docker_settings.png"> <img src="img/docker_settings.png">
### Share drives in Docker settings ### Share drives in Docker settings
Tis is an important and required configuration step in order to build the bits from the build-container so it has access to the solution files.<p> This is an important and required configuration step in order to build the bits from the build-container so it has access to the solution files.<p>
You need to share the drives from Settings-> Shared Drives in the "Docker for Windows" configuration. You need to share the drives from Settings-> Shared Drives in the "Docker for Windows" configuration.
If you don't do this, you will get an error when trying to build from te container, like "Cannot create container for service yourApplication: C: drive is not shared". <p> If you don't do this, you will get an error when trying to build from the container, like "Cannot create container for service your Application: C: drive is not shared". <p>
The drive you'll need to share depends on where you place your source code. The drive you'll need to share depends on where you place your source code.
<img src="img/docker_settings_shared_drives.png"> <img src="img/docker_settings_shared_drives.png">