Page History

Docker

Images

This page was created using Windows as host container (Docker Desktop WSL 2 backend), but equivalent steps can be used for any Linux with Mono Framework as host container.

System Requirements

To make use of this feature, the following system requirements need to be matched.

• Install Docker.
• Windows 10 64-bit: Pro, Enterprise, or Education (Build 17134 or later). For Windows 10 Home, see Install Docker Desktop on Windows Home.
• Hyper-V and Containers Windows features must be enabled.
• The following hardware prerequisites are required to successfully run Client Hyper-V on Windows 10:
  • 64-bit processor with Second Level Address Translation (SLAT).
  • 4GB system RAM.
  • BIOS-level hardware virtualization support must be enabled in the BIOS. For more information, see Virtualization.

Configuration Procedure

Copying Folders and Runtime Files

After installing Docker and fs-9.1.12, copy the files and subfolders from ”.. fs-9.1” to the Docker’s temporary folder, as in the image.

Image Removed

In the image, the Bin is the temporary folder.

document provides guidance on using Docker images for deploying applications. Although most of the examples are based on creating Docker images for Linux, these steps are also applicable when using Windows containers, or if the application inside Docker is running on Windows.

Pre-built Docker Images

You do not need to create a new image from scratch, as we provide two ready-to-use images:

1. TWebServices

This image only installs the communication server. You use it by sending the necessary files from another computer via the software itself, connecting to the device, and transferring the files. This allows for upgrading the product without replacing the entire Docker image. 

→ See Docker with TWebServices for more information.

2. Full Product

This image contains all the product files, except for the solution itself. The advantage of this option is that it provides faster setup and easier file management, especially when dealing with a large number of files.

→ See Docker with Full Product for more information.

Custom Docker Generation

The choice of image depends on the scenario, as each has its own advantages. Consider which one is more suitable based on your specific requirements.

If you need to create a custom image, please refer to Custom Docker Generation.

Running the Image

The following information is valid regardless of which image has been loaded into Docker. Ensure to review the running instructions that apply to your setup.

→ Learn more at Running Docker Image.

The HTML5 subfolder is only necessary if Web Clients will access pages from runtime. DevExpress and Sync- Fusion files are only necessary if Smart Clients will access displays from runtime.

Also, only the protocol drivers used by the project need to be copied (Ex: MODBUS.xml and T.ProtocolDriver.MODBUS.dll). The size of the image depends on which files will be used by the project.

The Project file (.tproj) and all other necessary files (e.g.: vc redist, etc) should also be copied to the temporary folder.

Copying License and Argument Files

Create a RemoteLicenseService.config file and copy it to the temporary folder. The syntax is:

RemoteServer=<IpAddress>:<PortNumber>
// IP:Port where the licensing server is Running RemoteServer=192.168.1.1:3100

Image Removed

Create an Arguments.config file and copy it to the temporary folder. The syntax is:

/project:C:\App\<DockerTest>.tproj // Project file name (mandatory)
/docker // (mandatory)

Creating Docker File

Create a Dockerfile file based on existent image containing .NET Framework v4.6.2 or higher, (necessary by FramworX). Example:

FROM mcr.microsoft.com/dotnet/framework/runtime 
WORKDIR /app
COPY bin .
RUN C:\app\vc_redist.x64.exe /quiet /install 
RUN C:\app\vc_redist.x86.exe /quiet /install
ENTRYPOINT ["TServer.exe", "/args:Arguments.config"]

Notes on this procedure:

• Image from “microsoft.com/dotnet/framework/runtime” is used as initial image.
• In this example, all files from the temporary folder (Bin) will be copied to the “App“ folder (on image).
• 3 VC redist files will be installed via the RUN command.
• TServer will be executed using the parameters defined in the Arguments.config file.

To build the image, execute the following via the CMD command:

docker build -t fs . // dot (.) IS IMPORTANT!!!

Image Removed

 To run the image, execute the following via the CMD command:

docker run --memory=4096m --cpus=4 fs
// Min Recommended 4 GB Mem and 4 CPU cores

//or specifying the port:
docker run -p 3101:3101 fs

Image Removed

Image Removed

Image Removed

Useful Links About Docker

• Deploying a .NET Application with Docker.
• How to Dockerize Windows Applications: The 5 Steps.
• Windows container build fails to install vcredist.
• Use volumes.
• How to Set Up Postgres using Docker
• Attach to a process running on a Docker container.

In this section...