[QUESTION] Please, answer +1 if the solution is working properly for you (Through VS2017 or CLI environment)

[CESARDELATORRE]

A small favor, can you answer +1 to this thread if the solution is working for you (Through VS2017 or CLI environment)? - Bits compilation-Deploy-Run in Docker.
We'd like to know if the environment/solution is working for most of the people or not.

Better if you specify what environment you are using, like answering any of the following:

+1 (VS2017)
+1 (CLI)
+1 (Both)

Answer with a -1 if you have issues and you couldn't make it work (compile/deploy/run to Docker), any of the following:

-1 (VS2017)
-1 (CLI)
-1 (Both)

We could create a survey, but we're not looking for specific statistics jus a sense of how it is working for the majority, and this way based on issues might be quicker for you guys than going to surveymonkey or anything like that.

Thank you! :)

[kifjj]

+1 (Windows CLI, on Win10 Entr, RAM 7GB, got a lot of problems with SQL Container, managed to make it work after assigning docker 4352 MB and freeing RAM) ... wondering what HW is required to develop seriously with containers in real world scenarios. Any points?

[CESARDELATORRE]

@kifjj That's why we mentioned to set at least 4096 MB of memory to Docker and recommend a 16GB ram machine in the setup instructions. Take into account that this is only because SQL Server container requirements in a dev or testing environment where you spin everything up as containers. In a real production environment it is recommended to take out the DBs from Docker and put your Databases in a High Available system like Azure SQL DBA or a SQL Server cluster, on-premises. So the memory you'd need for that would be less.
Your microservices using .NET Core need very small amounts of memory, so you can have many and that won't be, usually, the issue in dev-test environments.
For a development/testing Docker environment, a 16GB machine would be good for most of the scenarios. It depends on how many "infrastructure containers" (like SQL, Redis and others) you have included. But usually, 16GB would be good to go for most dev/test environments.
For production, it really depends how scalable you'll need your system to be. When using an orchestrator (not just Docker) like Docker Swarm, Kubernetes, Meals DCOS in Azure Container Service or using Azure Service Fabric, it will depend on how many instances per microservice-type you want to have for high scalability. Not just memory but number of VMs, as well.
In short, HW requirements? it really depends on how large is your application in regards infrastructure (that impacts dev/test) and how scalable you want it to be in production

[CESARDELATORRE]

+1 (Both environments, CLI & VS2017) - Windows 10 Enterprise, RAM 16GB. Testing on Multiple machines.
:)

[HarshaRaikar]

Hi CESAR

I am getting timeout error when the MVC application first starts.
At: CatalogService.cs line 54.
dataString = await _apiClient.GetStringAsync(catalogUrl);

VS2017, windows 10 , 16GB RAM

[HarshaRaikar]

Oops. It was docker memory i guess. I set it to 4096MB and it started working now. :)

[dsrodenas]

+1 (VS2017) - Windows 10 Enterprise, RAM 16GB

[harrchen]

I tried to install the solution to Server 2016 with VS2017 without success. There doesn't seem to be a suitable docker installation for Windows 2016. I tried to install docker via powershell but cannot find a way to perform necessary configuration as outlined in this document. The reason I want to use Windows 2016 is that I cannot create a windows 10 image in my azure subscription.

[harrchen]

Also just realized that docker for windows will not work for Azure VMs. As such, is there a way to have the eShop sample app setup and running in Azure?

[kifjj]

@CESARDELATORRE thanks for your explanation. Everything makes sense, just a point I am missing.
Since in prod SQL Srv will not be in a container (which makes total sense) wouldn't be better to keep it out even in dev?

[eiximenis]

Hi @kifjj
One reason for using SQL Server in a container is for helping with managing external dependencies in development. We are not using only SQL Server but also Redis (in the Basket microservice), and RabbitMQ for microservice-to-microservice communication (still not in master branch but merged soon).
Forcing everyone to install and configure all these external dependencies would prevent most people to run the application. By using all these dependencies in Docker container you only need to pull the repo, build the images and everything is working fine.
Of course you can use SQL Server standalone: just update docker-compose files and everything should be fine :)

Thanks!

[CESARDELATORRE]

@kifjj @eiximenis Reasons given by eiximenis (Eduard) plus:
When using databases on containers that are spin-up and populated with the same sample data, that makes a perfect scenario for Integration-Tests, as the tests are predictable based on the same set of data.
However, you can of course have your databases on any regular SQL Server on-premises or Azure SQL DB. You'll just need to create the DB, change the connection-strings, and you're done. Even the sample data can be populated to those databases, too., as we do that with EF code.

One more point, you cannot use VMs in Azure for a DEVELOPMENT environment with "Docker for Windows" that would need a nested VM in Hyper-V, and that is not supported in Azure. However, you could, of course, deploy the containers to an Azure Linux VM that would be a Docker Linux host, for testing/production environment, but not development with Visual Studio, etc..

[mktitan]

+1 VS17. Looks great.

[FDUdannychen]

+1 VS2017, Win 10.
By the way "ordering.api" depends on "sql.data", if anyone always fails with "PrepareForLaunch" task failed, pulling sql.data(microsoft/mssql-server-linux) blabla error, you can manually pull the image before debugging, using docker pull microsoft/mssql-server-linux.

[geminiyellow]

+1 (CLI) mac

but when i try to check the web feature, there are some errors.

RAM: 8G

[CESARDELATORRE]

@geminiyellow What errors are you getting? - Remember, related to the Identity Authentication container based on IdentityServer4, when deploying from a Mac, you need to use the "production" docker-compose.prod.yml because the by default 10.0.75.1 IP is only available when using Docker for Windows.
Afaik that IP is not used in a Mac. So you need to explicitly set your external IP in the .env file at https://github.com/dotnet/eShopOnContainers/blob/master/.env

"localhost" won't work from the Mac when authenticating and the redirection because of that reason, you'll need to always use an specific IP when using the Mac.
In a real production system you would also use any specific DNS name for the Docker host or orchestrator DNS name.

[kbulte]

+1 (VS2017) Win 10 Pro, RAM 16GB

[mjrousos]

+1 (Both) Windows 10 Pro, 32 GB RAM.

I did have to change the VS startup project to the Docker project (which wasn't mentioned in the 'main steps') but that's mentioned in the full instructions and was pretty clearly needed. :)

[VhatAmI]

+1 (VS2017)

[dongdongmao]

i want know that can Visual Studio for Mac 2017 run the solution ?

[CESARDELATORRE]

@dongdongmao Not currently. Probably in the future.
Visual Studio for Mac still doesn't support Docker containers as VS 2017 for Windows does.
What you could use is Visual Studio Code for Mac, as editor and using its Docker extension: https://code.visualstudio.com/docs/languages/dockerfile

Then, using Docker CLI like docker-compose build/up from bash to build images and to deploy the containers.

[dongdongmao]

+1 (CLI) mac

but when i click LOGIN an unhandled exception occurred while processing the request.

InvalidOperationException: IDX10803: Unable to obtain configuration from: 'http://10.0.75.1:5105/.well-known/openid-configuration'.
Microsoft.IdentityModel.Protocols.ConfigurationManagerd__24.MoveNext()

[andrelmp]

VS 2017
ERROR: for sql.data Cannot start service sql.data: driver failed programming external connectivity on endpoint dockercompose3536241391_sql.data_1 (e4672897e3ee71a9cbebcb666e9034ccca0d97d5756d18fe8275ba3331c51049): Error starting userland proxy: Bind for 0.0.0.0:5433: unexpected error Permission denied

[CESARDELATORRE]

@andrelmp Hey! Did you set up Docker Community (aka Docker for Windows) with the required amount of memory? - At least 4096 GB for Docker, as specified in the setting up instructions here:
https://github.com/dotnet/eShopOnContainers/wiki/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment

Also here:
https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-docker

If you did, try re-starting Docker.. Looks like you are having an "environment issue".

Can you start any SQL Server container by itself? like the following Docker CLI commands:
docker pull microsoft/mssql-server-linux
docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=<YourStrong!Passw0rd>' -p 1433:1433 -d microsoft/mssql-server-Linux

You should probably face the same issue if you didn't set up the required memory for Docker.

[andrelmp]

wow that was fast! thank you @CESARDELATORRE
is exactly the memory issue on docker host

[ChristianWeyer]

+1 for CLI (macOS). After having set Docker to 4GB RAM.

But when running docker container ls I get this - and I am missing the Basket API, right (according to https://github.com/dotnet/eShopOnContainers/wiki/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code)#testing-all-the-applications-and-microservices)?

[ChristianWeyer]

BTW; when building the SPA, building the SPA with npm is successful.
But when executing docker-compose -f docker-compose.ci.build.yml up I get this error:

eShopOnContainers git:(dev) ✗ Docker-compose -f docker-compose.ci.build.yml up
Creating eshoponcontainers_ci-build_1
Attaching to eshoponcontainers_ci-build_1
ci-build_1  | /src/src/Web/WebSPA /src
ci-build_1  |
ci-build_1  | > [email protected] install /src/src/Web/WebSPA/node_modules/node-sass
ci-build_1  | > node scripts/install.js
ci-build_1  |
ci-build_1  | node-sass build Binary found at /src/src/Web/WebSPA/node_modules/node-sass/vendor/linux-x64-48/binding.node
ci-build_1  |
ci-build_1  | > [email protected] postinstall /src/src/Web/WebSPA/node_modules/node-sass
ci-build_1  | > node scripts/build.js
ci-build_1  |
ci-build_1  | Binary found at /src/src/Web/WebSPA/node_modules/node-sass/vendor/linux-x64-48/binding.node
ci-build_1  | Testing binary
ci-build_1  | Bus error
ci-build_1  |
ci-build_1  | npm ERR! Linux 4.9.13-moby
ci-build_1  | npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "rebuild" "node-sass"
ci-build_1  | npm ERR! node v6.10.0
ci-build_1  | npm ERR! npm  v3.10.10
ci-build_1  | npm ERR! code ELIFECYCLE
ci-build_1  | npm ERR! [email protected] postinstall: `node scripts/build.js`
ci-build_1  | npm ERR! Exit status 135
ci-build_1  | npm ERR!
ci-build_1  | npm ERR! Failed at the [email protected] postinstall script 'node scripts/build.js'.
ci-build_1  | npm ERR! Make sure you have the latest version of node.js and npm installed.
ci-build_1  | npm ERR! If you do, this is most likely a problem with the node-sass package,
ci-build_1  | npm ERR! not with npm itself.
ci-build_1  | npm ERR! Tell the author that this fails on your system:
ci-build_1  | npm ERR!     node scripts/build.js
ci-build_1  | npm ERR! You can get information on how to open an issue for this project with:
ci-build_1  | npm ERR!     npm bugs node-sass
ci-build_1  | npm ERR! Or if that isn't available, you can get their info via:
ci-build_1  | npm ERR!     npm owner ls node-sass
ci-build_1  | npm ERR! There is likely additional logging output above.
ci-build_1  |
ci-build_1  | npm ERR! Please include the following file with any support request:
ci-build_1  | npm ERR!     /src/src/Web/WebSPA/npm-debug.log
eshoponcontainers_ci-build_1 exited with code 1

[CESARDELATORRE]

@ChristianWeyer
Did you try to run this first from the CLI:
npm rebuild node-sass

before running the docker-compose -f docker-compose.ci.build.yml up ?

But that should be done from the compose execution…, too...

Can you create an issue specific for Mac environment so we track it down when possible?

Thanks for the feedback.

[rjdebona]

Hi, i'm trying to up project CLI

Im facing problem with mssql, Identity catalog was created
Microsoft.eShopOnContainers.Services.IdentityDB - OK Ceated

but CatalogDB was not:

Microsoft.eShopOnContainers.Services.CatalogDb - N OK

I'm missing something?

[mvelosop]

Hi @rjdebona,

I don't remember anyone having this problem, did you assign the 4 GB RAM that the setup guide specifies?

[rjdebona]

I setup 3.5GB. mssql is up.
There anyway to force this creation as ef migration with update-database?

[mvelosop]

Perhaps if you try spinning up only the SQL Server container with

docker-compose up sql.data 

And you configure the server in the connection string to localhost, 5433 or 10.0.75.1, 5433 you might get it.

Hope this helps.

[mvelosop]

Hi @richard-ashby,

It seems a Mac issue, would you create an issue so we continue the conversation there?

[richard-ashby]

Hi @mvelosop

It seems a Mac issue, would you create an issue so we continue the conversation there?

OK will do ASAP, BTW I need to reinstall VS2017 for Mac before I can re-test as I had to remove it yesterday due to other reason (un-related to this issue).

[rjdebona]

Perhaps if you try spinning up only the SQL Server container with

docker-compose up sql.data 

And you configure the server in the connection string to localhost, 5433 or 10.0.75.1, 5433 you might get it.

Hope this helps.

Did you say change string in app.settings of each API?

[mvelosop]

@rjdebona, you'd only have to do it in the four microservices that use an SQL Server DB, and just to migrate the DB, but I'm not sure this would solve your issue, since it seems to be a memory issue.

[rjdebona]

+1 @mvelosop that's correct, i up from 3,5GB to 4GB and problems were solved. Thanks!

[mvelosop]

Glad to know it's working for you @rjdebona!

[umitkavala]

+1 (VS2017) on dev branch

[sxuvep]

+1. DOCKER CLI on MAC.

[jwmiller5]

+1 (VS2017) on dev branch

[Sn3b]

+1 CLI on Windows
-1 VS2017
+1 VS2019

[LeeDumond]

+1 VS2019 on Windows 10

[pjgeutjens]

+1 VS2019 on Windows 10
+1 CLI on Mac
-1 VS2019 for Mac

pretty sure the -1 is this issue: https://developercommunity.visualstudio.com/content/problem/459912/docker-support-in-aspnet-core-project-fails-to-run.html

docker containers are up but not running the solutions..

[betonogueira]

+1 VS2019 on Windows 10
+1 CLI on Windows 10

[nilukshan]

How to deploy this type of project in Azure Kubernates Service using docker-compose?

[mvelosop]

Hi @nilukshan, you might want to take a look at the wiki page: https://github.com/dotnet-architecture/eShopOnContainers/wiki/10.-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts

However, there's an issue I'm working on now and if fails when trying to deploy to local Kubernetes.

[sarthakvijayvergiya]

-1 (VS2019) on dev branch in Windows 10

Severity Code Description Project File Line Suppression State
Error (Line: 218, Col: 9, Idx: 5557) - (Line: 218, Col: 9, Idx: 5557): Expected 'MappingStart', got 'SequenceStart' (at Line: 218, Col: 9, Idx: 5557). docker-compose C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets 300

[mvelosop]

Hi @sarthakvijayvergiya, as metioned in issue #1073, this seemed to be a VS issue, but it was "workarounded" in commit 33fb3a7.

[lloydmonteiro]

-1 vs2019 community....Internal server error on Login page

[mvelosop]

Hi @lloydmonteiro, could you create an issue with the details, please?

[hdduong]

+1 VS2017 on Windows 10

[RL-FrankieJay]

Hi @nilukshan, you might want to take a look at the wiki page: https://github.com/dotnet-architecture/eShopOnContainers/wiki/10.-Deploying-to-Kubernetes-(AKS-and-local)-using-Helm-Charts

However, there's an issue I'm working on now and if fails when trying to deploy to local Kubernetes.

were you able to find solution to the issue of deploying locally to kubernetes?

[PrashantDeherkar]

-1 CLI on Windows 10
+1 VS2019 on Windows 10

Note: I have followed the setup instructions including Docker Advanced settings and Windows Firewall settings as per documents:

• For CLI - https://github.com/dotnet-architecture/eShopOnContainers/wiki/03.-Setting-the-eShopOnContainers-solution-up-in-a-Windows-CLI-environment-(dotnet-CLI,-Docker-CLI-and-VS-Code)
• For VS2019 - https://github.com/dotnet-architecture/eShopOnContainers/wiki/02.-Setting-eShopOnContainers-in-a-Visual-Studio-2017-environment

Issue Details below-

-1 CLI on Win10 issues:

Also see attached file for CLI docker logs generated.
eShopOnContainers-CLI-docker-logs.log

a) Error building "identity.api", "webstatus" and "webmvc"=>
libman.json : error LIB002: The "[email protected]" library could not be resolved by the "unpkg" provider [/src/src/Services/Identity/Identity.API/Identity.API.csproj]
One or more libraries failed to restore ERROR: Service 'identity.api' failed to build: The command '/bin/sh -c dotnet publish -c Release -o /app' returned a non-zero code: 1
-- Need to manually update respective "libman.json" files in local folder to use provider "cdnjs" instead of "unpkg"

b) Later facing error building and running API Gateways "webshoppingapigw", "webmarketingapigw", "mobilemarketingapigw", "mobileshoppingapigw":
webshoppingapigw_1 | Unhandled Exception: System.IO.FileNotFoundException: The configuration file 'configuration/configuration.json' was not found and is not optional. The physical path is '/app/configuration/configuration.json'.
webshoppingapigw_1 | at
Microsoft.Extensions.Configuration.FileConfigurationProvider.Load(Boolean reload)
webshoppingapigw_1 | at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load()
webshoppingapigw_1 | at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList`1 providers)
webshoppingapigw_1 | at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
webshoppingapigw_1 | at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
webshoppingapigw_1 | at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
webshoppingapigw_1 | at OcelotApiGw.Program.BuildWebHost(String[] args) in /src/src/ApiGateways/ApiGw-Base/Program.cs:line 42
webshoppingapigw_1 | at OcelotApiGw.Program.Main(String[] args) in /src/src/ApiGateways/ApiGw-Base/Program.cs:line 19
eshoponcontainers_webshoppingapigw_1 exited with code 139

c) WebSPA error screen image (similar issues 'Catalog service error' in WebMVC app):

**+1 VS2019 - resolved below issue by disabling Windows Firewall settings for vpnkit as described at link #295 (comment) **

Built the docker-compose CS Project.
a) WebMVC Exception when clicked Login menu on Home page
Error - InvalidOperationException: IDX20803: Unable to obtain configuration from: '[PII is hidden]'.

b) WebSPA Exception when clicked Login menu on Home page

Note that Identity Application is working as shown in below image:

[mvelosop]

Closing this issue now as it's not being tracked any more, please create a regular issue in case of getting started problems.