Current status: Which engine, best practices

Hello,
I am trying to find the correct information on what engine/ solution works with what FW. There are different old manuals online which seems to be not up-to-date anymore:

[Node-RED and getting started with Docker - PLCnext Community](https://www.plcnext-community.net/makersblog/node-red-and-getting-started-with-docker/)




_A Docker container can be used to run a node-RED server on a PLCnext device. Although the other method described here is a little faster. The use of OCI containers comes with some advantages. For example when repeatedly using the same packages for an application it can be useful to build a standard image and just download […]_


Can I get confirmation that podman is the way to go with 2025.0? Is it preinstalled (like mentioned in this comment <https://github.com/PLCnext/Docker_GettingStarted>)?  
Are there some examples with Podman, docker files, how to run them, how to build images, how to transfer them etc?  
My goal is to have a minimal ros2 installation that can read/ write to some GDS vars. I though about using gRPC...  
  
Thanks a lot!



Hello robin4clx,
podman is the way to go.
I found the info here: Using OCI containers
We don’t have a separate example, have a look at the Podman documentation.
The following tutorial might give you an introduction to Podman: Tutorials — Podman documentation

I hoped to find an in-depth example also with cross-compiling for arm32v7 etc.
Need to figure that out then

Hello @robin4clx,

I just came across your post and saw that you’re planning to build a minimal application to exchange data with ROS.
For this purpose, we’ve developed a solution called ROSBridge:
GitHub - PLCnext/PLCnext-ROS-bridge: The PLCnext-ROS-bridge enables the whole power of the open source Roboter Operating System (ROS) for the IEC61131 world. · GitHub

This bridge allows you build a custom interface to exchange data between ROS and our PLCnext.

Unfortunately, it is not available for ARM32 in the context of ROS 2. According to REP‑2000, ARM32 is classified as a Tier 3 platform, which means that no official ROS 2 binarys and therefore also images are produced by the ROS build farm.
Because of this, you would need to build ROS from source or rely on third‑party images.

If you want to learn more about the ROSBridge or discuss your specific use case, feel free to get in touch with us through our contact form:
https://www.phoenixcontact.com/agv

BR

agv_db