Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3104

podman from 9.1 cannot start a container when installed on RHEL 9.0

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • rhel-9.4
    • rhel-9.1.0
    • crun
    • None
    • Important
    • sst_container_tools
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • If docs needed, set a value
    • None

      Description of problem:
      We are using quite an old RHEL 9.0 image. Since 9.1 was released, we began to see the following message when we install podman there and run podman run -it --rm ubi8 bash (both rootful and rootless):

      /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check
      ERRO[0008] Removing container 78466eb964523e69916ef96289126ee971f1aed795b957b5738e256d46742d69 from runtime after creation failed
      Error: OCI runtime error: crun: /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check

      Version-Release number of selected component (if applicable):
      podman-4.2.0-7.el9_1.x86_64

      How reproducible:
      100%

      Steps to Reproduce:
      1. Install RHEL 9.0 GA and subscribe
      2. dnf install -y podman
      3. podman run -it --rm ubi8 bash

      Actual results:
      /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check
      ERRO[0010] Removing container bfa6142606da0b33dec26f1def21847215519860f4040c542c7c1e2591286f08 from runtime after creation failed
      Error: OCI runtime error: crun: /usr/bin/crun: symbol lookup error: /usr/bin/crun: undefined symbol: criu_feature_check

      Expected results:
      I get bash in a container

            rhn-support-jnovy Jindrich Novy
            obudai@redhat.com Ondrej Budai
            Container Runtime Eng Bot Container Runtime Eng Bot
            Container Runtime Bugs Bot Container Runtime Bugs Bot
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: