From fc32abf65606822b01870f860ffaf51cb4b00a55 Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Wed, 25 Oct 2017 17:46:44 -0700 Subject: [PATCH] Updated 99. FAQ (Frequently Asked Questions) (markdown) --- 99.-FAQ-(Frequently-Asked-Questions).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/99.-FAQ-(Frequently-Asked-Questions).md b/99.-FAQ-(Frequently-Asked-Questions).md index 65d284b..0263c36 100644 --- a/99.-FAQ-(Frequently-Asked-Questions).md +++ b/99.-FAQ-(Frequently-Asked-Questions).md @@ -66,7 +66,7 @@ If response is received the problem is that the request from a container cannot 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) -Another possibility is that the ASP.NET Identity database was not generated right or in time by EF Migrations when the app first started because the SQL container was too slow to be ready for the Identity service. You can have a workaround for that by increasing the time of retry with exponential backoff of the EF Contexts within the Identity.API service. Or simply, try re-deploying the app into Docker. +Another possibility is that the ASP.NET Identity database was not generated right or in time by EF Migrations when the app first started because the SQL container was too slow to be ready for the Identity service. You can have a workaround for that by increasing the number of retries with exponential backoff of the EF Contexts within the Identity.API service (i.e. increase maxRetryCount at the sqlOptions provided to the ConfigureDbContext). Or simply, try re-deploying the app into Docker. #### Deploying in a Mac with Docker for Mac In a Mac, youn cannot use the 10.0.75.1 IP, so you need to change that in the `docker-compose.override.yml` file, replace the IdentityUrl environment variable (or any place where the IP 10.0.75.1 is used) with: