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

Fix folder for windows networking scripts

Miguel Veloso 2019-12-17 13:51:53 +00:00
parent 5114850f80
commit 72f7fc0b93
4 changed files with 23 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Docker-configuration.md

@ -31,7 +31,7 @@ The drive you'll need to share depends on where you place your source code.
IMPORTANT: Ports 5100 to 5105 must be open in the local Firewall, so authentication to the STS (Security Token Service container, based on IdentityServer) can be done through the 10.0.75.1 IP, which should be available and already setup by Docker. These ports are also needed for client remote apps like Xamarin app or SPA app in a remote browser. IMPORTANT: Ports 5100 to 5105 must be open in the local Firewall, so authentication to the STS (Security Token Service container, based on IdentityServer) can be done through the 10.0.75.1 IP, which should be available and already setup by Docker. These ports are also needed for client remote apps like Xamarin app or SPA app in a remote browser.
You can manually create a rule in your local firewall in your development machine or you can just run the <b>add-firewall-rules-for-sts-auth-thru-docker.ps1</b> script available in the solution's **cli-windows** folder. You can manually create a rule in your local firewall in your development machine or you can just run the **`add-firewall-rules-for-sts-auth-thru-docker.ps1`** script available in the solution's **`deploy\windows\`** folder.
![](images/Docker-configuration/firewall-rule-for-eshop.png) ![](images/Docker-configuration/firewall-rule-for-eshop.png)

18
Frecuent-errors.md

@ -2,14 +2,14 @@ These are the most frequent errors encountered when running eShopOnContainers fo
> **CONTENT** > **CONTENT**
- [When trying to log in from the MVC app I get an error](#When-trying-to-log-in-from-the-MVC-app-I-get-an-error) - [When trying to log in from the MVC app I get an error](#when-trying-to-log-in-from-the-mvc-app-i-get-an-error)
- [Deploying in Windows with Docker for Windows](#Deploying-in-Windows-with-Docker-for-Windows) - [Deploying in Windows with Docker for Windows](#deploying-in-windows-with-docker-for-windows)
- [Deploying in a Mac with Docker for Mac](#Deploying-in-a-Mac-with-Docker-for-Mac) - [Deploying in a Mac with Docker for Mac](#deploying-in-a-mac-with-docker-for-mac)
- [Additional resources](#Additional-resources) - [Additional resources](#additional-resources)
- [The SQL Server container is not running](#The-SQL-Server-container-is-not-running) - [The SQL Server container is not running](#the-sql-server-container-is-not-running)
- [When I run the solution (using Visual Studio or the CLI) I get warnings like 'The ESHOP_AZURE_XXXX variable is not set...'](#When-I-run-the-solution-using-Visual-Studio-or-the-CLI-I-get-warnings-like-The-ESHOPAZUREXXXX-variable-is-not-set) - [When I run the solution (using Visual Studio or the CLI) I get warnings like 'The ESHOP_AZURE_XXXX variable is not set...'](#when-i-run-the-solution-using-visual-studio-or-the-cli-i-get-warnings-like-the-eshopazurexxxx-variable-is-not-set)
- [When I run 'docker-compose up' I get an error like ERROR: Service 'xxxxx' failed to build: COPY failed: stat ...: no such file or directory](#When-I-run-docker-compose-up-I-get-an-error-like-ERROR-Service-xxxxx-failed-to-build-COPY-failed-stat--no-such-file-or-directory) - [When I run 'docker-compose up' I get an error like ERROR: Service 'xxxxx' failed to build: COPY failed: stat ...: no such file or directory](#when-i-run-docker-compose-up-i-get-an-error-like-error-service-xxxxx-failed-to-build-copy-failed-stat--no-such-file-or-directory)
- [When I try to run the solution in 'Docker for Windows' (on the Linux VM) I get the error: 'Did you mean to run dotnet SDK commands?'](#When-I-try-to-run-the-solution-in-Docker-for-Windows-on-the-Linux-VM-I-get-the-error-Did-you-mean-to-run-dotnet-SDK-commands) - [When I try to run the solution in 'Docker for Windows' (on the Linux VM) I get the error: 'Did you mean to run dotnet SDK commands?'](#when-i-try-to-run-the-solution-in-docker-for-windows-on-the-linux-vm-i-get-the-error-did-you-mean-to-run-dotnet-sdk-commands)
## When trying to log in from the MVC app I get an error ## When trying to log in from the MVC app I get an error
@ -24,7 +24,7 @@ First open a browser and navigate to <http://10.0.75.1:5105/.well-known/openid-c
If response is received the problem is that the request from a container cannot reach the `10.0.75.1` (which is the IP of the host machine inside the DockerNAT). Be sure that: If response is received the problem is that the request from a container cannot reach the `10.0.75.1` (which is the IP of the host machine inside the DockerNAT). Be sure that:
- You have opened the ports of the firewall (run the script `cli-windows\add-firewall-rules-for-sts-auth-thru-docker.ps1` - You have opened the ports of the firewall (run the script **`deploy\windows\add-firewall-rules-for-sts-auth-thru-docker.ps1`**)
If this do not solved your problem ensure that the `vpnkit` of the firewall is disabled. For more info refer to @huangmaoyixxx's comment in [issue #295](https://github.com/dotnet-architecture/eShopOnContainers/issues/295) If this do not solved your problem ensure that the `vpnkit` of the firewall is disabled. For more info refer to @huangmaoyixxx's comment in [issue #295](https://github.com/dotnet-architecture/eShopOnContainers/issues/295)

8
Mac-setup.md

@ -178,7 +178,7 @@ git clone https://github.com/dotnet-architecture/eShopOnContainers.git
### 3. Build the application ### 3. Build the application
```console ```console
cd eShopOnContainers cd eShopOnContainers\src
docker-compose build docker-compose build
``` ```
@ -186,7 +186,7 @@ While building the docker images should take between 15 and 30 minutes to comple
![](images/Mac-setup/building-eshoponcontainers.png) ![](images/Mac-setup/building-eshoponcontainers.png)
The first time you run this command it'll take some more additional time as it needs to pull/download the dotnet/core/aspnet and SDK images, 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 `dotnet/core/aspnet` and SDK images, so it'll take its time.
When the `docker-compose build` command finishes, you can check out with Docker CLI the images created with the following Docker command: When the `docker-compose build` command finishes, you can check out with Docker CLI the images created with the following Docker command:
@ -198,9 +198,9 @@ docker images
Those are the Docker images available in your local image repository. Those are the Docker images available in your local image repository.
You might have additional images, but you should see, at least, the the custom images starting with the prefix "eshop/" which is the name of the eShopOnContainers images repo. You might have additional images, but you should see, at least, the the custom images starting with the prefix `eshop/` which is the name of the eShopOnContainers images repo.
The images starting with `<none>` haven't been tagged with a name and are intermediate images of the build process. Other named images that don't start with "eshop/" are official base-images like the microsoft/aspnetcore or the SQL Server for Linux images. The images starting with `<none>` haven't been tagged with a name and are intermediate images of the build process. Other named images that don't start with `eshop/` are official base-images like the `mcr.microsoft.com/dotnet` or the SQL Server for Linux images.
### 4. Deploy to the local Docker host ### 4. Deploy to the local Docker host

6
Windows-setup.md

@ -26,7 +26,7 @@ The approach followed is to have the app running from the CLI first, since it's
- [Build and run the application with F5 or Ctrl+F5](#build-and-run-the-application-with-f5-or-ctrlf5) - [Build and run the application with F5 or Ctrl+F5](#build-and-run-the-application-with-f5-or-ctrlf5)
- [Set docker-compose as the default StartUp project](#set-docker-compose-as-the-default-startup-project) - [Set docker-compose as the default StartUp project](#set-docker-compose-as-the-default-startup-project)
- [Debug with several breakpoints across the multiple containers/projects](#debug-with-several-breakpoints-across-the-multiple-containersprojects) - [Debug with several breakpoints across the multiple containers/projects](#debug-with-several-breakpoints-across-the-multiple-containersprojects)
- [Issue with "Visual Studio 2017 Tools for Docker" and network proxies/firewalls](#issue-with-%22visual-studio-2017-tools-for-docker%22-and-network-proxiesfirewalls) - [Issue with &quot;Visual Studio 2017 Tools for Docker&quot; and network proxies/firewalls](#issue-with-quotvisual-studio-2017-tools-for-dockerquot-and-network-proxiesfirewalls)
- [Optional - Use Visual Studio Code](#optional---use-visual-studio-code) - [Optional - Use Visual Studio Code](#optional---use-visual-studio-code)
- [Explore the code](#explore-the-code) - [Explore the code](#explore-the-code)
- [Low memory configuration](#low-memory-configuration) - [Low memory configuration](#low-memory-configuration)
@ -67,7 +67,7 @@ The drive you'll need to share depends on where you place your source code.
IMPORTANT: Ports 5100 to 5105 must be open in the local Firewall, so authentication to the STS (Security Token Service container, based on IdentityServer) can be done through the 10.0.75.1 IP, which should be available and already setup by Docker. These ports are also needed for client remote apps like Xamarin app or SPA app in a remote browser. IMPORTANT: Ports 5100 to 5105 must be open in the local Firewall, so authentication to the STS (Security Token Service container, based on IdentityServer) can be done through the 10.0.75.1 IP, which should be available and already setup by Docker. These ports are also needed for client remote apps like Xamarin app or SPA app in a remote browser.
You can manually create a rule in your local firewall in your development machine or you can just run the **add-firewall-rules-for-sts-auth-thru-docker.ps1** script available in the solution's **cli-windows** folder. You can manually create a rule in your local firewall in your development machine or you can just run the **add-firewall-rules-for-sts-auth-thru-docker.ps1** script available in the solution's **`deploy\windows\`** folder.
![](images/Windows-setup/firewall-rule-for-eshop.png) ![](images/Windows-setup/firewall-rule-for-eshop.png)
@ -98,7 +98,7 @@ git clone https://github.com/dotnet-architecture/eShopOnContainers.git
### 3. Build the application ### 3. Build the application
```console ```console
cd eShopOnContainers cd eShopOnContainers\src
docker-compose build docker-compose build
``` ```