I found something that might be the main cause for this: /etc/os-release features the ID=debian entry on my reference system; When i temporarily override my DUTs os-release to feature ID=debian or similar its able to detect Podman. Is there a way to fix this behaviour?
Hello, CODESYS seems to have problems finding the container engine. In the "Deploy Control SL" window, after connecting via ssh, it simply says: [INFORMATION] Connected successfully! [INFORMATION] Successfully connected to target (192.168.4.199) [WARNING] Error detecting container architecture running podman info yields normal results. My podman info output is as follows: home/Admin$ podman info host: arch: amd64 buildahVersion: 1.35.3 cgroupControllers: - cpu - memory - pids cgroupManager: systemd...