Bug 2097694

Hello,

Some more information about the env. Mostly, it's from our QE job[1]. If more data are needed, please let me know.

Red Hat Enterprise Linux release 9.0 (Plow)

+ podman version
Client:       Podman Engine
Version:      4.0.2
API Version:  4.0.2
Go Version:   go1.17.7

Built:      Thu May 19 14:18:11 2022
OS/Arch:    linux/amd64

+ podman info
host:
  arch: amd64
  buildahVersion: 1.24.1
  cgroupControllers:
  - cpuset
  - cpu
  - io
  - memory
  - hugetlb
  - pids
  - rdma
  - misc
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.0-1.el9.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.0, commit: 3a898eb433ae426e729088ccdc2bdae44a3164da'
  cpus: 8
  distribution:
    distribution: '"rhel"'
    version: "9.0"
  eventLogger: journald
  hostname: undercloud1702-0.redhat.local
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.14.0-70.13.1.el9_0.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree: 19000770560
  memTotal: 24930738176
  networkBackend: netavark
  ociRuntime:
    name: crun
    package: crun-1.4.4-2.el9_0.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.4.4
      commit: 6521fcc5806f20f6187eb933f9f45130c86da230
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_NET_RAW,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: false
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /bin/slirp4netns
    package: slirp4netns-1.1.12-4.el9.x86_64
    version: |-
      slirp4netns version 1.1.12
      commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.2
  swapFree: 0
  swapTotal: 0
  uptime: 24m 59.07s
plugins:
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  192.168.24.1:
    Blocked: false
    Insecure: true
    Location: 192.168.24.1
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: 192.168.24.1
  192.168.24.3:
    Blocked: false
    Insecure: true
    Location: 192.168.24.3
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: 192.168.24.3
  search:
  - registry.redhat.io
  - registry.access.redhat.com
  - registry.fedoraproject.org
  - registry.centos.org
  - docker.io
  undercloud1702-0.ctlplane.redhat.local:
    Blocked: false
    Insecure: true
    Location: undercloud1702-0.ctlplane.redhat.local
    MirrorByDigestOnly: false
    Mirrors: null
    Prefix: undercloud1702-0.ctlplane.redhat.local
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 38
    paused: 0
    running: 7
    stopped: 31
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 16
  runRoot: /run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 4.0.2
  Built: 1652984291
  BuiltTime: Thu May 19 14:18:11 2022
  GitCommit: ""
  GoVersion: go1.17.7
  OsArch: linux/amd64
  Version: 4.0.2




[1] https://rhos-ci-staging-jenkins.lab.eng.tlv2.redhat.com/view/DFG/view/df/view/deployment/job/DFG-df-deployment-17.0-virthost-3cont_2comp_3ceph-ceph-ipv4-geneve-satellite-local-registry/

Already fixed in upstream
https://github.com/containers/podman/pull/14582
Fixed podman 4.2

Assigning to Jindrich for any further BZ/packaging needs.

Hello,

Would it be possible to ship it in the el9 repositories (afaik, still "beta") ? OSP needs this patched version asap in order to unblock all our QE jobs related to subscription-manager :(. Maybe a backport of that patch in 4.1 (or 4.0, since that one is currently shipped) would be good?

Thank you for your feedback!

Cheers,

C.

@jnovy Thoughts on Cedric's comment: https://bugzilla.redhat.com/show_bug.cgi?id=2097694#c6 ?

We have two options:

1) release podman-4.2
2) backport Giuseppe's https://github.com/containers/podman/pull/14582 into the v4.1.1-rhel branch and I will point RHEL9.1 and RHEL8.7 to consume content from there.

What do you think Tom is the best option?

@jnovy I chose door number 2 and backported to the v4.1.1-rhel branch.  All yours!

https://github.com/containers/podman/pull/14861

This bug has been verified on podman-4.1.1-3.el9.x86_64.

[root@kvm-07-guest25 ~]# podman run -v /run:/run quay.io/libpod/alpine true
[root@kvm-07-guest25 ~]# systemd-detect-virt
kvm
[root@kvm-07-guest25 ~]# ls /run/.containerenv
ls: cannot access '/run/.containerenv': No such file or directory

This bug has been verified on podman-4.1.1-3.el9.x86_64.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: podman security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7954