From 8ba2f64c2f67c6de463611c2745ef579946f16d4 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Tue, 2 Jan 2018 17:21:51 -0800 Subject: [PATCH] Updated 03. Setting the eShopOnContainers solution up in a Windows CLI environment (dotnet CLI, Docker CLI and VS Code) (markdown) --- ...I-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code).md | 9 +++++---- 1 file changed, 5 insertions(+), 4 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 3ead1b4..74ba20c 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 @@ -150,10 +150,11 @@ With a single command you can deploy the whole solution into your local Docker h - 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 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. - 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: + + - The next time you run "docker-compose up" again (you don't need to repeat it now), because now you already have all the base images downloaded and registered in your local repo and your custom images built and ready to go, it'll be much faster since it just needs to deploy the containers, like the following screenshot: @@ -164,7 +165,7 @@ With a single command you can deploy the whole solution into your local Docker h - You can also check out with Docker CLI the images generated by typing in the PowerShell console the command: `docker images` - Those Docker images are the ones you have available in your local image repository in your machine. +Those Docker images are the ones you have available in your local image repository in your machine. You might have additional images, but at least, you should see the following list of images which are 6 custom images starting with the prefix "eshop" which is the name of the image repo. The rest of the images that are not starting with "eshop" will probably be official base-images like the microsoft/aspnetcore or the SQL Server for Linux images.