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

Updated 99. FAQ (Frequently Asked Questions) (markdown)

Cesar De la Torre 2017-10-04 14:55:29 -07:00
parent 57f5f30c46
commit 5d537a682e
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
99.-FAQ-(Frequently-Asked-Questions).md

@ -35,7 +35,8 @@ pwd:guest
### The SQL Server container is not running
It looks like the SQL container tried to start but then it exited?
If I do a "docker ps -a", the STATUS column for the SQL container does NOT show a status of "Up" but shows the STATUS as "Exited".
Workaround: Usually this is due to not enough memory assigned to the Docker Host Linux VM. Note that sometimes after installing a "Docker for Windows" update it might have reset the value and it might be 2GB again, which is not enough for the SQL container. Set, at least, 4GB of memory to the Docker Host in "Docker for Windows" settings.
Workaround: Usually this is due to not enough memory assigned to the Docker Host Linux VM.
IMPORTANT: Note that sometimes after installing a "Docker for Windows" update it might have reset the assigned memory value and it might be 2GB again (see Docker issue https://github.com/docker/for-win/issues/1169), which is not enough for the SQL container. Set, at least, 4GB of memory to the Docker Host in "Docker for Windows" settings.
### When I run the solution(using Visual Studio 2017 or the CLI) I see one or more warnings like "The ESHOP_AZURE_XXXX variable is not set. Defaulting to a blank string."