CodesysTutorial: Deploy Virtual PLC on Ubuntu Core & Debian

Summary

This video provides an in-depth guide on deploying a virtual PLC using Docker Compose on Ubuntu Core, covering both AMD and ARM processors. The process starts with building a Docker image, followed by creating a Docker Compose file to configure the containers. The tutorial also shows how to deploy the PLC on a virtual machine, Raspberry Pi, and Ubuntu Core, detailing network mapping, image pulling, and permissions. The video emphasizes managing multiple virtual PLCs and accessing them via OPC, offering practical steps for both standard and ARM-based systems.

Takeaways

• 😀 Virtual PLC can be deployed using Docker Compose on both AMD and ARM processors on Ubuntu Core.
• 😀 To build a Docker image, first download and extract the necessary package, then organize files into the required folders for different processor architectures.
• 😀 A Docker build command is used to create the image after configuring the necessary parameters, including version and file name.
• 😀 When building the image, ensure that the file references match with the Docker configuration to avoid errors during the build process.
• 😀 After creating the Docker image, use it to deploy virtual PLCs on a system like Debian by utilizing Docker Compose files.
• 😀 A Docker Compose file is configured with service names, container names, volumes, and ports, and is used to start the virtual PLC container.
• 😀 You can run multiple virtual PLC containers by modifying the container and service names, as well as the port mappings, to avoid conflicts.
• 😀 For deploying on Ubuntu Core, Docker must be installed using Snap, and permissions may need to be adjusted before proceeding with image pulls.
• 😀 For virtual machine environments, ensure that the network is properly mapped to allow external access to the containerized virtual PLC.
• 😀 For Raspberry Pi ARM-based systems, the process is similar, but the architecture-specific Docker images need to be used, and network configurations must be adjusted to ensure accessibility.
• 😀 Accessing the virtual PLC via OPC client can be done once network configurations and permissions (like anonymous login) are set correctly.

Q & A

What is the primary focus of this video?

The primary focus of the video is to explain how to deploy a virtual PLC using Docker Compose on both AMD and ARM processors, specifically on Ubuntu Core and Debian systems.

What is the first step in creating a Docker image for the virtual PLC?

The first step is to download the necessary package and extract it. After extraction, you need to navigate to the folder containing the delivery and dependency files.

How do you build the Docker image for the virtual PLC?

To build the Docker image, you need to go into the extracted folder, modify the Docker build command to match the specific version and file names, and then run the Docker build command from the terminal.

What error might occur when building the Docker image and how is it resolved?

The error that may occur is related to unresolved links to repoman.com. This can be fixed by modifying the Dockerfile to point to the correct repository and saving the changes before rebuilding the image.

How can you create multiple virtual PLCs with Docker Compose?

To create multiple virtual PLCs, you can duplicate the Docker Compose configuration, change the container names, service names, host names, and volume paths, and then run the `docker compose up -d` command to start the containers.

What is the role of the Docker Compose file in this deployment?

The Docker Compose file defines the services, container names, volumes, ports, and capabilities needed for the virtual PLC deployment. It ensures that the containers are started with the correct configuration.

How can you access the deployed virtual PLC once it is running?

Once the virtual PLC is running, you can access it using the IP address and port number provided by the Docker container. In some cases, network mapping may be needed for external access, especially when running on virtual machines or on Ubuntu Core.

What additional step is required when deploying the virtual PLC on Ubuntu Core?

When deploying the virtual PLC on Ubuntu Core, you need to install Docker using the `sudo snap install docker` command and configure network settings to allow external access by mapping the correct network bridge.

What challenge may occur when trying to access the virtual PLC on Ubuntu Core, and how can it be solved?

A potential challenge is that the IP address of the virtual PLC may not be accessible externally. To solve this, you need to configure network settings, such as enabling multipass network mapping and setting up a bridge network for external access.

How is the process of deploying the virtual PLC similar across different platforms like Debian, Ubuntu Core, and ARM devices?

The process is largely the same across platforms: you pull the appropriate Docker image, configure the Docker Compose file, and then use `docker compose up -d` to start the virtual PLC. The only differences are the platform-specific image IDs and network configuration.