New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
CESARDELATORRE opened this Issue Mar 9, 2017 · 238 comments

Comments

Projects
None yet
@CESARDELATORRE
Collaborator

CESARDELATORRE commented Mar 9, 2017

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! :)

@CESARDELATORRE CESARDELATORRE changed the title from [QUESTION] Answer +1 if the solution is working for you (Through VS2017 or CLI environment) to [QUESTION] Answer +1 if the solution is working properly for you (Through VS2017 or CLI environment) Mar 9, 2017

@CESARDELATORRE CESARDELATORRE changed the title from [QUESTION] Answer +1 if the solution is working properly for you (Through VS2017 or CLI environment) to [QUESTION] Please, answer +1 if the solution is working properly for you (Through VS2017 or CLI environment) Mar 10, 2017

@kifjj

This comment has been minimized.

Show comment
Hide comment
@kifjj

kifjj Mar 11, 2017

+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?

kifjj commented Mar 11, 2017

+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

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Mar 11, 2017

Collaborator

@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

Collaborator

CESARDELATORRE commented Mar 11, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Mar 11, 2017

Collaborator

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

Collaborator

CESARDELATORRE commented Mar 11, 2017

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

@HarshaRaikar

This comment has been minimized.

Show comment
Hide comment
@HarshaRaikar

HarshaRaikar Mar 11, 2017

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 commented Mar 11, 2017

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

This comment has been minimized.

Show comment
Hide comment
@HarshaRaikar

HarshaRaikar Mar 11, 2017

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

HarshaRaikar commented Mar 11, 2017

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

@dsrodenas

This comment has been minimized.

Show comment
Hide comment
@dsrodenas

dsrodenas Mar 13, 2017

Collaborator

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

Collaborator

dsrodenas commented Mar 13, 2017

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

@harrchen

This comment has been minimized.

Show comment
Hide comment
@harrchen

harrchen Mar 14, 2017

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 commented Mar 14, 2017

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

This comment has been minimized.

Show comment
Hide comment
@harrchen

harrchen Mar 14, 2017

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?

harrchen commented Mar 14, 2017

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

This comment has been minimized.

Show comment
Hide comment
@kifjj

kifjj Mar 14, 2017

@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?

kifjj commented Mar 14, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@eiximenis

eiximenis Mar 14, 2017

Collaborator

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!

Collaborator

eiximenis commented Mar 14, 2017

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

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Mar 14, 2017

Collaborator

@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..

Collaborator

CESARDELATORRE commented Mar 14, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@mktitan

mktitan Mar 16, 2017

+1 VS17. Looks great.

mktitan commented Mar 16, 2017

+1 VS17. Looks great.

@FDUdannychen

This comment has been minimized.

Show comment
Hide comment
@FDUdannychen

FDUdannychen Mar 17, 2017

+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.

FDUdannychen commented Mar 17, 2017

+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

This comment has been minimized.

Show comment
Hide comment
@geminiyellow

geminiyellow Mar 18, 2017

+1 (CLI) mac

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

RAM: 8G

geminiyellow commented Mar 18, 2017

+1 (CLI) mac

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

RAM: 8G

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Mar 18, 2017

Collaborator

@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.

Collaborator

CESARDELATORRE commented Mar 18, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@kbulte

kbulte Mar 19, 2017

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

kbulte commented Mar 19, 2017

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

@mjrousos

This comment has been minimized.

Show comment
Hide comment
@mjrousos

mjrousos Mar 20, 2017

Collaborator

+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. :)

Collaborator

mjrousos commented Mar 20, 2017

+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

This comment has been minimized.

Show comment
Hide comment
@VhatAmI

VhatAmI Mar 24, 2017

+1 (VS2017)

VhatAmI commented Mar 24, 2017

+1 (VS2017)

@dongdongmao

This comment has been minimized.

Show comment
Hide comment
@dongdongmao

dongdongmao Mar 28, 2017

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

dongdongmao commented Mar 28, 2017

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

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Mar 29, 2017

Collaborator

@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.

Collaborator

CESARDELATORRE commented Mar 29, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@dongdongmao

dongdongmao Apr 3, 2017

+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()

dongdongmao commented Apr 3, 2017

+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

This comment has been minimized.

Show comment
Hide comment
@andrelmp

andrelmp Apr 4, 2017

Contributor

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

Contributor

andrelmp commented Apr 4, 2017

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

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Apr 4, 2017

Collaborator

@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.

Collaborator

CESARDELATORRE commented Apr 4, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@andrelmp

andrelmp Apr 4, 2017

Contributor

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

Contributor

andrelmp commented Apr 4, 2017

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

@ChristianWeyer

This comment has been minimized.

Show comment
Hide comment
@ChristianWeyer

ChristianWeyer Apr 5, 2017

+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)?

image

ChristianWeyer commented Apr 5, 2017

+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)?

image

@ChristianWeyer

This comment has been minimized.

Show comment
Hide comment
@ChristianWeyer

ChristianWeyer Apr 5, 2017

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  | > node-sass@4.5.0 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  | > node-sass@4.5.0 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! node-sass@4.5.0 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 node-sass@4.5.0 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

ChristianWeyer commented Apr 5, 2017

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  | > node-sass@4.5.0 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  | > node-sass@4.5.0 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! node-sass@4.5.0 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 node-sass@4.5.0 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

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Apr 5, 2017

Collaborator

@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.

Collaborator

CESARDELATORRE commented Apr 5, 2017

@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.

@SSathappa

This comment has been minimized.

Show comment
Hide comment
@SSathappa

SSathappa Jun 11, 2018

+1 (VS2017) 15.7.3 Win 10 Pro with 16 GB RAM

SSathappa commented Jun 11, 2018

+1 (VS2017) 15.7.3 Win 10 Pro with 16 GB RAM

@wayne-o

This comment has been minimized.

Show comment
Hide comment
@wayne-o

wayne-o Jun 11, 2018

Hi - I am just looking through the code so haven't tried to run it yet - just a quick question - is the Ocelot stuff going to replace the other APIs or are they designed to work side-by-side?

wayne-o commented Jun 11, 2018

Hi - I am just looking through the code so haven't tried to run it yet - just a quick question - is the Ocelot stuff going to replace the other APIs or are they designed to work side-by-side?

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jun 12, 2018

Collaborator

@wayne-o - No, Ocelot API Gateways are just like a Façade, acting like reverse-proxies re-routing to the existing microservices we already had.
API Gateways offer further value than just reverse-proxy. See info about Ocelot for that.

Collaborator

CESARDELATORRE commented Jun 12, 2018

@wayne-o - No, Ocelot API Gateways are just like a Façade, acting like reverse-proxies re-routing to the existing microservices we already had.
API Gateways offer further value than just reverse-proxy. See info about Ocelot for that.

@wayne-o

This comment has been minimized.

Show comment
Hide comment
@wayne-o

wayne-o Jun 13, 2018

@CESARDELATORRE could you give me an example of where you are using an API Gateway where Ocelot would not be suitable please? I have read the ocelot docs a few times over now as I find it really interesting - I am considering replacing my existing API gateway with it but would like to know some examples of where Ocelot is not suitable so i can see if I am about to hit some road blocks :)

wayne-o commented Jun 13, 2018

@CESARDELATORRE could you give me an example of where you are using an API Gateway where Ocelot would not be suitable please? I have read the ocelot docs a few times over now as I find it really interesting - I am considering replacing my existing API gateway with it but would like to know some examples of where Ocelot is not suitable so i can see if I am about to hit some road blocks :)

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jun 13, 2018

Collaborator

@wayne-o - If you just need API Gateways features, Ocelot is suitable for most of the cases. There are large customers using it in scalable solutions, like Tencent (WebChat app) in China :https://www.tencent.com/en-us/system.html

However, in some cases where you are also selling your APIs to customers, there are many additional features that you might want to have, like what you have in Azure API Management, with assets like a developer portal, publisher portal, etc. and many more features you can see here:
https://azure.microsoft.com/en-us/services/api-management/

Collaborator

CESARDELATORRE commented Jun 13, 2018

@wayne-o - If you just need API Gateways features, Ocelot is suitable for most of the cases. There are large customers using it in scalable solutions, like Tencent (WebChat app) in China :https://www.tencent.com/en-us/system.html

However, in some cases where you are also selling your APIs to customers, there are many additional features that you might want to have, like what you have in Azure API Management, with assets like a developer portal, publisher portal, etc. and many more features you can see here:
https://azure.microsoft.com/en-us/services/api-management/

@kolluri-rk

This comment has been minimized.

Show comment
Hide comment
@kolluri-rk

kolluri-rk Jun 14, 2018

+1 (CLI) mac
-1 (VS2017 7.5.2) mac master branch

Build fails:
screen shot 2018-06-12 at 5 23 55 pm

I have opened docker-compose.vs.debug.g.yml and found this. looks like $nuget_volume_mapping_mobilemarketingapigw$ is causing the issue.

screen shot 2018-06-13 at 10 55 17 pm

kolluri-rk commented Jun 14, 2018

+1 (CLI) mac
-1 (VS2017 7.5.2) mac master branch

Build fails:
screen shot 2018-06-12 at 5 23 55 pm

I have opened docker-compose.vs.debug.g.yml and found this. looks like $nuget_volume_mapping_mobilemarketingapigw$ is causing the issue.

screen shot 2018-06-13 at 10 55 17 pm

@harrchen88

This comment has been minimized.

Show comment
Hide comment
@harrchen88

harrchen88 Jun 14, 2018

+1 CLI Windows 10 (surface book with 8GB) with Docker for windows

harrchen88 commented Jun 14, 2018

+1 CLI Windows 10 (surface book with 8GB) with Docker for windows

@wayne-o

This comment has been minimized.

Show comment
Hide comment
@wayne-o

wayne-o Jun 14, 2018

@CESARDELATORRE thanks for the response :) I mean't in relation to the non Ocelot BFF API's we have in this project - what is the reason for keeping them going? I think they are called aggregators - here.

From the Ocelot docs I can see that we can aggregate the results of multiple calls to the backend micro services and return as one response. So I guess my question is - why are these aggregator projects being maintained when Ocelot can do aggregation. I'm wondering what this case is so that I am aware of any short comings in Ocelot that I might not be aware of that could trip me up down the line - or potentially be a feature request for Ocelot :)

wayne-o commented Jun 14, 2018

@CESARDELATORRE thanks for the response :) I mean't in relation to the non Ocelot BFF API's we have in this project - what is the reason for keeping them going? I think they are called aggregators - here.

From the Ocelot docs I can see that we can aggregate the results of multiple calls to the backend micro services and return as one response. So I guess my question is - why are these aggregator projects being maintained when Ocelot can do aggregation. I'm wondering what this case is so that I am aware of any short comings in Ocelot that I might not be aware of that could trip me up down the line - or potentially be a feature request for Ocelot :)

@eiximenis

This comment has been minimized.

Show comment
Hide comment
@eiximenis

eiximenis Jun 14, 2018

Collaborator

Hi @kolluri-rk
This seems to be an issue about Visual Studio For Mac.

@CESARDELATORRE Seems that VS For Mac 7.5.2 has the same Docker Tools that VS2017 15.6 had. To build the dev branch of eShopOnContainers you need the Docker Tools provided with VS2017 15.7. We should check when VS For Mac will get those equivalent Docker Tools.

Collaborator

eiximenis commented Jun 14, 2018

Hi @kolluri-rk
This seems to be an issue about Visual Studio For Mac.

@CESARDELATORRE Seems that VS For Mac 7.5.2 has the same Docker Tools that VS2017 15.6 had. To build the dev branch of eShopOnContainers you need the Docker Tools provided with VS2017 15.7. We should check when VS For Mac will get those equivalent Docker Tools.

@eiximenis

This comment has been minimized.

Show comment
Hide comment
@eiximenis

eiximenis Jun 14, 2018

Collaborator

Hi @wayne-o

When started using Ocelot for eShopOnContainers no aggregation support was available, so we ended up building our custom aggregators. Thats the reason :)

Collaborator

eiximenis commented Jun 14, 2018

Hi @wayne-o

When started using Ocelot for eShopOnContainers no aggregation support was available, so we ended up building our custom aggregators. Thats the reason :)

@wayne-o

This comment has been minimized.

Show comment
Hide comment
@wayne-o

wayne-o Jun 14, 2018

wayne-o commented Jun 14, 2018

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jun 14, 2018

Collaborator

@wayne-o - Also, discussing about Aggregators with Tom Pallister (from Ocelot), we preferred to create our own custom aggregators because they are more flexible by using our code.
The way you use aggregation with Ocelot is pretty simple but might not be flexible enough in many situations.

Collaborator

CESARDELATORRE commented Jun 14, 2018

@wayne-o - Also, discussing about Aggregators with Tom Pallister (from Ocelot), we preferred to create our own custom aggregators because they are more flexible by using our code.
The way you use aggregation with Ocelot is pretty simple but might not be flexible enough in many situations.

@wayne-o

This comment has been minimized.

Show comment
Hide comment
@wayne-o

wayne-o Jun 14, 2018

wayne-o commented Jun 14, 2018

@AndrewCapon

This comment has been minimized.

Show comment
Hide comment
@AndrewCapon

AndrewCapon Jun 14, 2018

The VS for Mac 2017 beta 7.6.0.947 also gives the same errors as 7.5.2

AndrewCapon commented Jun 14, 2018

The VS for Mac 2017 beta 7.6.0.947 also gives the same errors as 7.5.2

@AbaiCheng

This comment has been minimized.

Show comment
Hide comment
@AbaiCheng

AbaiCheng Jun 15, 2018

+1 (VS2017)

AbaiCheng commented Jun 15, 2018

+1 (VS2017)

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jun 15, 2018

Collaborator

@wayne-o - Thanks a lot for the feedback! 👍

Collaborator

CESARDELATORRE commented Jun 15, 2018

@wayne-o - Thanks a lot for the feedback! 👍

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jun 15, 2018

Collaborator

@AndrewCapon @kolluri-rk
Looks like it is a possible bug in VS for Mac. I have reported it to the VS Tools for Docker team and created an specific issue in our side, here:
#634

Any update will be posted in the issue.
Thanks for your feedback! 👍

Collaborator

CESARDELATORRE commented Jun 15, 2018

@AndrewCapon @kolluri-rk
Looks like it is a possible bug in VS for Mac. I have reported it to the VS Tools for Docker team and created an specific issue in our side, here:
#634

Any update will be posted in the issue.
Thanks for your feedback! 👍

@AndrewCapon

This comment has been minimized.

Show comment
Hide comment
@AndrewCapon

AndrewCapon Jun 16, 2018

@CESARDELATORRE thanks very much for doing that for us.

AndrewCapon commented Jun 16, 2018

@CESARDELATORRE thanks very much for doing that for us.

1 similar comment
@AndrewCapon

This comment has been minimized.

Show comment
Hide comment
@AndrewCapon

AndrewCapon Jun 16, 2018

@CESARDELATORRE thanks very much for doing that for us.

AndrewCapon commented Jun 16, 2018

@CESARDELATORRE thanks very much for doing that for us.

@kolluri-rk

This comment has been minimized.

Show comment
Hide comment
@kolluri-rk

kolluri-rk Jun 20, 2018

@CESARDELATORRE thank you so much. I will follow updates on that thread.

kolluri-rk commented Jun 20, 2018

@CESARDELATORRE thank you so much. I will follow updates on that thread.

@maulikk2000

This comment has been minimized.

Show comment
Hide comment
@maulikk2000

maulikk2000 Jul 2, 2018

@CESARDELATORRE What is the reason for using loggerFactory.AddAzureWebAppDiagnostics(); in WebStatus project?
As per doco (https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-2.1 ) ,

If targeting .NET Core, don't install the provider package or explicitly call AddAzureWebAppDiagnostics. The provider is automatically available to the app when the app is deployed to Azure App Service.

thanks,
Maulik Khandwala

maulikk2000 commented Jul 2, 2018

@CESARDELATORRE What is the reason for using loggerFactory.AddAzureWebAppDiagnostics(); in WebStatus project?
As per doco (https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-2.1 ) ,

If targeting .NET Core, don't install the provider package or explicitly call AddAzureWebAppDiagnostics. The provider is automatically available to the app when the app is deployed to Azure App Service.

thanks,
Maulik Khandwala

@hfleurygithub

This comment has been minimized.

Show comment
Hide comment
@hfleurygithub

hfleurygithub commented Jul 7, 2018

+1 (VS2017)

@arindams621

This comment has been minimized.

Show comment
Hide comment
@arindams621

arindams621 Jul 11, 2018

@CESARDELATORRE
Hello,

I have been looking into this app and have successfully set it up on a VM and it works smoothly with localhost. However I tried to put an ip and faced the below situations...Can you please help me understand where am I going wrong?

First Scenario:
Instead of loaclhost tried gave the public IP of my VM in the .env file and ran the app with a CI-CD pipeline. Used the docker-compose -f docker-compose.yml -f docker-compose.override.yml up
Issues:

  1. Here I am able to access the MVc app on 5100 port. But the images are not present for the items in the catalog. (though the Jenkins workspace is on the same VM itself)
  2. Whenever I try to Login, it says unauthorized client

Second Scenario:
Followed the step by step documentation and created all the Azure resources and updated the .env file with the IP..
Next updated the docker-compose.prod.yml file. And ran the command docker-compose -f docker-compose.yml -f docker-compose.prod.yml up.

  1. Here I am able to access the MVC app on PublicIP:5100. The Pics are present but the "Add to cart" functionality is disabled and am not able to click it to add anything to my cart.
  2. Whenever I click login, I get the login page and on entering the demousername/password and clicking on Login gives me the exception in the attachment Exception1.
  3. Whenever I try to register new user it gives me the error as in screenshot in the attachment of Exception2.
    !
    Exception1.txt
    exception2

exception2
Exception1.txt

I am not able to understand what needs to be done. Hence seeking help in this forum.

Regards,
AS

arindams621 commented Jul 11, 2018

@CESARDELATORRE
Hello,

I have been looking into this app and have successfully set it up on a VM and it works smoothly with localhost. However I tried to put an ip and faced the below situations...Can you please help me understand where am I going wrong?

First Scenario:
Instead of loaclhost tried gave the public IP of my VM in the .env file and ran the app with a CI-CD pipeline. Used the docker-compose -f docker-compose.yml -f docker-compose.override.yml up
Issues:

  1. Here I am able to access the MVc app on 5100 port. But the images are not present for the items in the catalog. (though the Jenkins workspace is on the same VM itself)
  2. Whenever I try to Login, it says unauthorized client

Second Scenario:
Followed the step by step documentation and created all the Azure resources and updated the .env file with the IP..
Next updated the docker-compose.prod.yml file. And ran the command docker-compose -f docker-compose.yml -f docker-compose.prod.yml up.

  1. Here I am able to access the MVC app on PublicIP:5100. The Pics are present but the "Add to cart" functionality is disabled and am not able to click it to add anything to my cart.
  2. Whenever I click login, I get the login page and on entering the demousername/password and clicking on Login gives me the exception in the attachment Exception1.
  3. Whenever I try to register new user it gives me the error as in screenshot in the attachment of Exception2.
    !
    Exception1.txt
    exception2

exception2
Exception1.txt

I am not able to understand what needs to be done. Hence seeking help in this forum.

Regards,
AS

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jul 11, 2018

Collaborator

@arindams621 - There are quite a few different issues/questions around your post..
Can you please create separated questions/topics in different ISSUES at the repo depending on the specific problems?
We'll try to provide some support/answers for topics directly related to eShopOnContainers, but about other issues related to your environment, we won't be able to help, as our time is very limited and must be restricted to issues related to eShopOnContainers in the dev environment, most of all.
Thanks,

Issues in Azure can get complex and depend on your infrastructure/environment, and we don't have time bandwidth for it.

Collaborator

CESARDELATORRE commented Jul 11, 2018

@arindams621 - There are quite a few different issues/questions around your post..
Can you please create separated questions/topics in different ISSUES at the repo depending on the specific problems?
We'll try to provide some support/answers for topics directly related to eShopOnContainers, but about other issues related to your environment, we won't be able to help, as our time is very limited and must be restricted to issues related to eShopOnContainers in the dev environment, most of all.
Thanks,

Issues in Azure can get complex and depend on your infrastructure/environment, and we don't have time bandwidth for it.

@arindams621

This comment has been minimized.

Show comment
Hide comment
@arindams621

arindams621 Jul 11, 2018

@CESARDELATORRE Thanks for the quick TAT. I do understand the time and bandwidth restrictions and hence am creating 2 main issues that I am looking forward to resolve with further directions/help.

arindams621 commented Jul 11, 2018

@CESARDELATORRE Thanks for the quick TAT. I do understand the time and bandwidth restrictions and hence am creating 2 main issues that I am looking forward to resolve with further directions/help.

@Bughunter666

This comment has been minimized.

Show comment
Hide comment
@Bughunter666

Bughunter666 Jul 18, 2018

The documentation is stating that this sample is supposed to run either on Service Bus or on Azure Container Kubernetes Services as these are basically the tested environments.

I would like to deploy on Azure App Service though. Any chances to get this to work?

@maulikk2000 You seem to have managed (?) to get this up and running when avoiding to use AzureAppServicesLoggerFactoryExtensions.AddAzureWebAppDiagnostics?

Bughunter666 commented Jul 18, 2018

The documentation is stating that this sample is supposed to run either on Service Bus or on Azure Container Kubernetes Services as these are basically the tested environments.

I would like to deploy on Azure App Service though. Any chances to get this to work?

@maulikk2000 You seem to have managed (?) to get this up and running when avoiding to use AzureAppServicesLoggerFactoryExtensions.AddAzureWebAppDiagnostics?

@Bughunter666

This comment has been minimized.

Show comment
Hide comment
@Bughunter666

Bughunter666 Jul 19, 2018

@CESARDELATORRE The documentation is stating that this sample is supposed to run either on Service Bus or on Azure Container Kubernetes Services as these are basically the tested environments.
I would like to deploy on Azure App Service though. Any chances to get this to work or should it work but it has just not been (fully) tested yet?

Bughunter666 commented Jul 19, 2018

@CESARDELATORRE The documentation is stating that this sample is supposed to run either on Service Bus or on Azure Container Kubernetes Services as these are basically the tested environments.
I would like to deploy on Azure App Service though. Any chances to get this to work or should it work but it has just not been (fully) tested yet?

@CESARDELATORRE

This comment has been minimized.

Show comment
Hide comment
@CESARDELATORRE

CESARDELATORRE Jul 25, 2018

Collaborator

@Bughunter666 - Azure App Service is not meant to be used as a deployment platform for a microservices-based application like eShopOnContainers.
Azure App Service is designed to host web apps, usually more like monolithic apps or coarse-grain N-Tier apps, but not fine-grain microservices (tens of microservices, for instance).

Best environments for microservices on containers are AKS or Service Fabric.

In addition, you cannot deploy infrastructure containers (like SQL container, RabbitMQ, Redis, etc.) into Azure App Service (only services using HTTP or HTTPS). You'd need to create all that infrastructure in other Azure's services (Azure SQL Database, Azure Service Bus and Redis as a service), which for a production environment is right, but for Dev/Test environments will take a lot more work than just deploying the whole eShopOnContainers into an orchestrator like AKS (Kubernetes).

About Azure Service Bus, it is opt-in in eShopOnContainers. The by default environment uses a RabbitMQ container, but we also support Azure Service Bus for the Event Bus abstraction.

Collaborator

CESARDELATORRE commented Jul 25, 2018

@Bughunter666 - Azure App Service is not meant to be used as a deployment platform for a microservices-based application like eShopOnContainers.
Azure App Service is designed to host web apps, usually more like monolithic apps or coarse-grain N-Tier apps, but not fine-grain microservices (tens of microservices, for instance).

Best environments for microservices on containers are AKS or Service Fabric.

In addition, you cannot deploy infrastructure containers (like SQL container, RabbitMQ, Redis, etc.) into Azure App Service (only services using HTTP or HTTPS). You'd need to create all that infrastructure in other Azure's services (Azure SQL Database, Azure Service Bus and Redis as a service), which for a production environment is right, but for Dev/Test environments will take a lot more work than just deploying the whole eShopOnContainers into an orchestrator like AKS (Kubernetes).

About Azure Service Bus, it is opt-in in eShopOnContainers. The by default environment uses a RabbitMQ container, but we also support Azure Service Bus for the Event Bus abstraction.

@cloudstrifebro

This comment has been minimized.

Show comment
Hide comment
@cloudstrifebro

cloudstrifebro Jul 31, 2018

+1 - got the identity provider (identity server 4) working by doing what @terolaakso said to do as well.

I also did this as well:
https://github.com/IdentityServer/IdentityServer3.Samples/tree/master/source/Certificates

cloudstrifebro commented Jul 31, 2018

+1 - got the identity provider (identity server 4) working by doing what @terolaakso said to do as well.

I also did this as well:
https://github.com/IdentityServer/IdentityServer3.Samples/tree/master/source/Certificates

@GadgetGeekUK

This comment has been minimized.

Show comment
Hide comment
@GadgetGeekUK

GadgetGeekUK Aug 3, 2018

Docker for Windows just doesn't work on my machine. How about Service Fabric?

GadgetGeekUK commented Aug 3, 2018

Docker for Windows just doesn't work on my machine. How about Service Fabric?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment