Deploy Control SL cant find Podman

denizerm
2025-10-22
7 days ago
  • denizerm - 2025-10-22

    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
      cgroupVersion: v2
      conmon:
        package: Unknown
        path: /usr/bin/conmon
        version: 'conmon version 2.1.10, commit: affab49967eb62f75d2a47398344ab053326289f'
      cpuUtilization:
        idlePercent: 99.36
        systemPercent: 0.3
        userPercent: 0.34
      cpus: 4
      databaseBackend: sqlite
      distribution:
        codename: scarthgap
        distribution: redagv
        version: 1.0.0
      eventLogger: journald
      freeLocks: 2040
      hostname: secure-automation-os
      idMappings:
        gidmap:
        - container_id: 0
          host_id: 1000
          size: 1
        - container_id: 1
          host_id: 100000
          size: 65536
        uidmap:
        - container_id: 0
          host_id: 1100
          size: 1
        - container_id: 1
          host_id: 100000
          size: 65536
      kernel: 6.6.65-intel-pk-standard
      linkmode: dynamic
      logDriver: journald
      memFree: 6115598336
      memTotal: 8086278144
      networkBackend: cni
      networkBackendInfo:
        backend: cni
        dns: {}
      ociRuntime:
        name: crun
        package: Unknown
        path: /usr/bin/crun
        version: |-
          crun version 1.14.3.0.0.0.8-89d44-dirty
          commit: 89d44467e3b410b73f2065756a12789be45b855b
          rundir: /run/user/1100/crun
          spec: 1.0.0
          +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
      os: linux
      pasta:
        executable: /usr/bin/pasta
        package: Unknown
        version: ""
      remoteSocket:
        exists: true
        path: /run/podman-shared/podman.sock
      security:
        apparmorEnabled: false
        capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
        rootless: true
        seccompEnabled: true
        seccompProfilePath: ""
        selinuxEnabled: false
      serviceIsRemote: true
      slirp4netns:
        executable: /usr/bin/slirp4netns
        package: Unknown
        version: |-
          slirp4netns version 1.2.0-beta.0+dev
          commit: unknown
          libslirp: 4.7.0
          SLIRP_CONFIG_VERSION_MAX: 4
          libseccomp: 2.5.5
      swapFree: 0
      swapTotal: 0
      uptime: 1h 36m 10.00s (Approximately 0.04 days)
      variant: ""
    plugins:
      authorization: null
      log:
      - k8s-file
      - none
      - passthrough
      - journald
      network:
      - bridge
      - macvlan
      - ipvlan
      volume:
      - local
    registries:
      localhost:5000:
        Blocked: false
        Insecure: true
        Location: localhost:5000
        MirrorByDigestOnly: false
        Mirrors: null
        Prefix: localhost:5000
        PullFromMirror: ""
      search:
      - localhost
    store:
      configFile: /home/serviceuser/.config/containers/storage.conf
      containerStore:
        number: 2
        paused: 0
        running: 2
        stopped: 0
      graphDriverName: overlay
      graphOptions: {}
      graphRoot: /data/containerfiles
      graphRootAllocated: 119952025600
      graphRootUsed: 13801246720
      graphStatus:
        Backing Filesystem: extfs
        Native Overlay Diff: "true"
        Supports d_type: "true"
        Supports shifting: "false"
        Supports volatile: "true"
        Using metacopy: "false"
      imageCopyTmpDir: /var/tmp
      imageStore:
        number: 4
      runRoot: /run/user/1100/containers
      transientStore: false
      volumePath: /data/containerfiles/volumes
    version:
      APIVersion: 5.0.2-dev
      Built: 1711987427
      BuiltTime: Mon Apr  1 16:03:47 2024
      GitCommit: bb81e85a430fa95d23a15b77c717fd68bf06ebf2
      GoVersion: go1.22.12
      Os: linux
    
     
  • denizerm - 7 days ago

    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?

     

Log in to post a comment.