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

podman restore with --pod failed to start the container with permission denied

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-8.10
    • container-selinux
    • None
    • None
    • None
    • rhel-sst-container-tools
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      Make a checkpoint for a container with pod and try to restore it from the checkpoint file. The container can not start up normally

      Please provide the package NVR for which bug is seen:

      module-container-tools-rhel8-8100020240105104119-82888897
      container-selinux-2.227.0-1.module+el8.10.0+21077+98b84d8a.noarch.rpm

      How reproducible:

      100%

      Steps to reproduce

      1. Create a pod and a container
        $ podman pod create --share uts,pid test
        $ podman run -d --pod test quay.io/libpod/alpine:latest top
      2. Create a checkpoint
        $ podman container checkpoint -e test.tar.gz ec1a442b5c467e83a59701cb596433aae12df4299651daefc3a4efb5269cb368
        ec1a442b5c467e83a59701cb596433aae12df4299651daefc3a4efb5269cb368
      3. Remove the old pod
        $ podman pod rm test
      4. Create a new pod and restore the container
        $ podman pod create --share uts,pid
        8bac85c57ae5e8eaa27076585ee09b476198fd5152ebd82caf5a65eecc7f651c
        $ podman container restore --pod 8bac85c57ae5e8eaa27076585ee09b476198fd5152ebd82caf5a65eecc7f651c -i test.tar.gz
      5. Check the container status and logs
        $ podman ps -a
        CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
        b8bd2f249f70 localhost/podman-pause:4.8.3-1704466083 23 seconds ago Up 7 seconds bfda738de26a-infra
        ec1a442b5c46 quay.io/libpod/alpine:latest top 7 seconds ago Exited (1) 2 seconds ago thirsty_lamarr
        $ podman logs ec1a442b5c46
        Mem: 2314220K used, 5568220K free, 9112K shrd, 4204K buff, 2063352K cached
        CPU: 0% usr 0% sys 0% nic 99% idle 0% io 0% irq 0% sirq
        Load average: 0.00 0.00 0.00 2/130 10
        PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
        6 0 root R 1568 0% 0 0% top
        top: can't open '/proc': Permission denied 0% /catatonit -P

      Expected results

      The container can be restore and runs without error

      Actual results

      Container exited with Permission denied error

      More details

      If we run the same steps after 'setenforce 0', the test will pass.

              dwalsh@redhat.com Daniel Walsh (Inactive)
              ypu@redhat.com Yiqiao Pu
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: