Trouble viewing images? Click on images to enlarge.

This article will walk you through the process of standing up a WebReports Docker Container for Linux.  In this example we are using the Docker Desktop for Windows. 

Requirements and Network Topology

For more information on the System Requirements and Network Topology, please read this article.

A Microsoft SQL Database is required for the WebReports application.  If you already have a Microsoft SQL Server Database running you can skip the Microsoft SQL Server Database Docker Container Setup steps.

A valid certificate is required for the WebReports application to run.  In the example below we are referencing a .pfx file, which is called when starting the Docker Image.  Please see your system documentation for creating a valid certificate/pfx file.

Microsoft SQL Server Database Docker Container Setup

1. Open Windows PowerShell

2. Modify then execute the following command to Install MS SQL. 

NOTE: The password is being set in this command, please change the orange text in the command to your desired password.

docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=FAg1sS%6W4hLLmKRtcSv" -e "MSSQL_PID=Express" -p 1433:1433 -d mcr.microsoft.com/mssql/server:2017-latest-ubuntu

3. Wait for the install to finish.

4. Execute the following command.

docker ps

5. Copy your CONTAINER ID.

6. Modify then execute the following command after replacing the text in orange with your copied CONTAINER ID from step 8.

docker inspect 4655319a9523

7. Copy the IPAddress.  This IP address will be used in the "DefaultConnection" section of the appsettings.json file.

WebReports Docker Image Setup

1. Run the following command, in Power Shell, to download the WebReports application.

docker pull bridgeworks/bridgeworksreportsweb

2. Wait for the download process to complete.

3. To start up the BridgeWorksWR Docker image, run the following command in Power Shell. 

It's important to replace SECRETPASSWORD with the password to your pfx file.  The command below references aspnetapp.pfx.  If your pfx file has a different name, please change the file name in the command to reflect your environment.

Please note: You MUST have a valid pfx file in your %USERPROFILE%\.aspnet\https directory.

docker run --name BridgeWorksWR -p 443:443 -e ASPNETCORE_URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=443 -e ASPNETCORE_Kestrel__Certificates__Default__Password="SECRETPASSWORD" -e ASPNETCORE_Kestrel__Certificates__Default__Path=/https/aspnetapp.pfx -v $env:USERPROFILE\.aspnet\https:/https/ --dns=8.8.8.8 -td bridgeworks/bridgeworksreportsweb:latest

4. Execute the following command to download the default appsettings.json file to the c:\temp directory (verify the c:\temp directory exists on your system or choose an alternate path).

docker cp BridgeWorksWR:/app/appsettings.json c:\temp

5. Edit the appsettings.json file with a text editor, and update DefaultConnection string, the LicenseKey and CompanyID.  All three are required for the docker container to start properly.  Save the file.

IPAddress - The IP address of your Microsoft SQL Server Instance.
User ID - The username to your Microsoft SQL Server Instance.
Password - The password to your Microsoft SQL Server Instance.

Example Connection String: "DefaultConnection": "Data Source=172.17.0.2,1433;Database=WebReportsV10;User Id=sa;Password=FAg1sS%6W4hLLmKRtcSv;Connect Timeout=60"

LicenseKey:  Available on your VDM subscription and registration information form.
CompanyID:  Available on your VDM subscription and registration information form.

6. Execute the following command to copy the modified appsettings.json file to the BridgeWorksWR image.

docker cp c:\temp\appsettings.json BridgeWorksWR:/app/

7. Go to Docker Desktop and start the BridgeWorksWR Image.  Confirm the BridgeWorksWR Docker Image has started and navigate to https://localhost.