Updated 08. Setting up and Deploying eShopOnContainers to Windows Containers (markdown)
parent
fc38c3bdb6
commit
b7547f340f
@ -23,21 +23,16 @@ In Windows 10 you need to set Docker to use "Windows container" instead of Linux
|
||||
|
||||
Then right click in the Docker icon on the notification bar and select the option "Switch to Windows Containers". If you don't see this option and see the option "Switch to Linux Containers" you're already using windows containers.
|
||||
|
||||
## Start Windows Containers
|
||||
## Deploy Windows Containers of eShopOnContaners
|
||||
Since eShopOnContainers is using Docker Multi-Stage builds, th ecompilation of the .NET application bits is now performed by Docker itself right before building the Docker images.
|
||||
|
||||
The easiest way to start the windows containers is using Powershell and use call the `cli-windows/start-windows-containers.ps1` script. This script will do three things:
|
||||
|
||||
1. Compile all projects (calling `cli-windows/build-bits.ps1`)
|
||||
2. Create windows images
|
||||
3. Start application
|
||||
|
||||
If don't want to compile all projects (because you have already published them) you can pass the parameter `-buildBits $false`:
|
||||
You can directly run `docker-compose build`:
|
||||
|
||||
```
|
||||
.\cli-windows\start-windows-containers.ps1 -buildBits $false
|
||||
docker-compose -f docker-compose-windows.yml build
|
||||
```
|
||||
|
||||
You can use `docker-compose` directly to start the containers if you want:
|
||||
Then deploy the containers with the specific configuration for Windows Containers:
|
||||
|
||||
```
|
||||
docker-compose -f docker-compose-windows.yml -f docker-compose.override.yml -f docker-compose.override.windows.yml up
|
||||
|
Loading…
x
Reference in New Issue
Block a user