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-03 10:08:57 -08:00
parent 1443a64f00
commit 935eaaff20
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -133,7 +133,7 @@ Then, run the following docker command:
![image](https://user-images.githubusercontent.com/1712635/34505989-cf652c88-efdd-11e7-97ac-7a97ac0c884a.png) ![image](https://user-images.githubusercontent.com/1712635/34505989-cf652c88-efdd-11e7-97ac-7a97ac0c884a.png)
The first time you run this command it'll take some more additional time as it needs to pull/download the aspnet-build image with the SDKs plus all the infrastructure images (SQL image, RabbitMQ image, MongoDB image, etc.), so it'll take its time. The first time you run this command it'll take some more additional time as it needs to pull/download the aspnet-build image with the SDKs, so it'll take its time.
It should take a few minutes to compile the .NET Core projects plus the SPA application (TypeScript/JavaScript). It should take a few minutes to compile the .NET Core projects plus the SPA application (TypeScript/JavaScript).
@ -154,7 +154,7 @@ With a single command you can deploy the whole solution into your local Docker h
<img src="img/cli-windows/docker-compose-up-1.png"> <img src="img/cli-windows/docker-compose-up-1.png">
Note that the first time you try to run any container (with docker run or docker-compose) it detects that it needs the base images you are using, like the SQL Server image and the Redis image, so it will pull or download those base images from the Internet, from the public repo at the Docker registry named DOCKER HUB, by pulling the "microsoft/mssql-server-linux" which is the base image for the SQL Server for Linux on containers, and the "library/redis" which is the base Redis image. Therefore, the first time you run docker-compose it might take a few minutes pulling those images before it spins up your custom containers. Note that the first time you try to run the application (with docker run or docker-compose) it detects that it needs a few related infrastructure images, like the SQL Server image, Redis image, RabbitMQ image, etc. so it will pull or download those base images from the Internet, from the public repo at the Docker registry named DOCKER HUB, by pulling the "microsoft/mssql-server-linux" which is the base image for the SQL Server for Linux on containers, and the "library/redis" which is the base Redis image, and so on. Therefore, the first time you run "docker-compose up" it might take a few minutes pulling those images before it spins up your custom containers.
Finally, you can see how the scripts waits after deploying all the containers: Finally, you can see how the scripts waits after deploying all the containers: