Dry goods, introduced the background of this Demo is not the main share of the Demo construction, environmental technology and code
first introduced to build
- Environment to build primary reference: https://github.com/dotnet-architecture/eShopOnContainers/wiki/Windows-setup#optional-use-visual-studio, I mainly add experience
- Download the latest version eShopOnContainers on GitHub, should be the Net Core 3.1 version
- Install the latest version of Windows for Docker, VS 2019 I was,
- Docker configuration environment has been mirrored address, use sqlserver ... I looked at the official suggested that I assigned four nuclear 5G, I use a proxy address Ali cloud images can also be used DaoCloud, and Ali cloud to be registered ...
- Open Docker-Compose.yml, manually download the need to use public image, until you can see all of the necessary public image in your docker environment, there netCore 3.1, mcr.microsoft.com/mssql/server:2017 -latest, Mongo, redis: alpine, rabbitmq: 3-management-alpine, envoyproxy / envoy: v1.11.1, datalust / seq: latest
- Pit 1: use the latest version, if you have the scientific tools of the Internet will affect HttpProxy settings, cause you could not pull off a mirror
- Pit 2: Microsoft sqlserver, netCore 3.1 image is downloaded from Microsoft's official domestic mirrored address is not my home telecommunications, mobile networks have tried to download very slow, my solution is to download on Ali cloud host, Once you have downloaded to export, and then I import the machine.
- Compile start docker-compose the project
- Pit 1: compilation process you will find a word in the compiled output will prompt VS inside "Building delayed until Bower / npm package complete recovery." In response did not wait long, I waited half an hour to no avail because there is a single. page angular Web project, the main card npm recovery problems may arise, and I stopped manually after the project began compiling start Docker, mode of operation is to have a small icon in the lower left corner of the background task VS, click open npm see the recovery process, click the red small box can be stopped.
- Pit 2: After startup, the browser automatically open localhost:. 5100 port, but you will find a 503 error reported, but the service is not available container all operating normally, reboot several times, the last to start found this error is inevitable the need to wait for 2-3 minutes, then refresh the access to, although I understand that the container starts, but the service has not been started to provide normal service, there may be a initialization process.
A summary of these detours to avoid all hope to help you
follow I will continue to update on some of the learning experience
