Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMiroslav Hostinsky
2022-05-11 07:49:02 UTC
Description of problem:
Unable to start container when running within pod
Version-Release number of selected component (if applicable):
podman-4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64
redhat-release-8.6-0.1.el8.x86_64
Steps to Reproduce:
# podman pod create --name pokus && podman run -it --rm --pod pokus alpine sh
926ab05b5645a351002a08418821594718fd9e8a5ff5172f573881d9798e773d
ERRO[0003] Starting some container dependencies
ERRO[0003] "runc: container_linux.go:380: starting container process caused: exec: \"/catatonit\": stat /catatonit: no such file or directory: OCI runtime attempted to invoke a command that was not found"
Error: error starting some containers: internal libpod error
Additional info:
It works when executed with /catatonit in pod
# podman pod create --name pokus -v /usr/libexec/catatonit/catatonit:/catatonit && podman run -it --rm --pod pokus alpine id
4f6222d18c2a355c1f58b478c36a2378cd844eb373cfb56c70f7d1748cf3d865
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video)
Miroslav, do you have podman-catatonit installed? Wasn't it forcibly removed by a chance?
Comment 4Miroslav Hostinsky
2022-05-11 08:21:09 UTC
Yes, it's installed:
podman-catatonit-4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64
It works if I create pod with bind mount of /usr/libexec/catatonit/catatonit:/catatonit (so it must be installed):
# podman pod create --name pokus -v /usr/libexec/catatonit/catatonit:/catatonit
Comment 5Miroslav Hostinsky
2022-05-11 08:30:40 UTC
I tried rootless podman instance from scratch and it works (I can see "/catatonit -P" running under pod):
$ podman system reset
$ podman pod create --name pokus
$ podman run -it --rm --pod pokus alpine sh
But, the issue above is when running podman (under root) upgraded from 3->4 (RHEL8.5->8.6). No "podman system reset"/clean install. Just upgraded from 8.5->8.6.
Comment 6Miroslav Hostinsky
2022-05-11 08:41:13 UTC
Older pods created with podman 3.x before upgrade work (running with /pause in pod). It seems that only new pod images are created without /catatonit.
Comment 7Valentin Rothberg
2022-05-11 09:16:48 UTC
@Miroslav, could you share the run with `podman --log-level=debug` and share the output?
Also, could you share the output of `podman images`? All for the failing root user.
Comment 11Miroslav Hostinsky
2022-05-11 19:31:49 UTC
It seems, that I found the problem. I created first pod with following command (there is no "localhost/podman-pause" image, it needs to be generated when first pod is created):
# podman pod create --name pod-httpd_php --uidmap=0:11900000:65536 --gidmap=0:11900000:65536 --ip 10.165.12.100 --ip6 2001:123:1234::1000
ERRO[0000] Can't add file /var/lib/containers/storage/overlay/1c4de2e5de894afaa1227fdb1eec59c2b763415cff277382d3bdf5e842aea1ee/merged/catatonit to tar: Host ID 0 cannot be mapped to a container ID
There is error (pod is not created), but still, "localhost/podman-pause" image is created with missing /catatonit (podman-pause image size around 3kB).
To fix the issue, I simply removed corrupted "localhost/podman-pause" image, and generated again first pod (in order to create "localhost/podman-pause") and then deleted it:
# podman pod create pokus && podman pod rm pokus
In this case, "localhost/podman-pause" is created with /catatonit binary and my complex pod (with uidmap) now works.
It seems, that there is difference in the podman behavior:
- podman 3.x - pod image is fetched from the hub: k8s.gcr.io/pause
- podman 4.x - pod image is generated locally on the first pod create and this process must be finished without error
Comment 15Valentin Rothberg
2022-05-12 08:01:47 UTC
Bug 2059066 looks different to me. The one here does not have a relation to containers.conf but there seems to be a bug when creating the _local_ pause image.
I am reopening as I can reproduce.
Comment 18Valentin Rothberg
2022-05-12 08:23:06 UTC
(In reply to Jindrich Novy from comment #17)
> It is a feature Valentin:
> https://github.com/containers/podman/issues/12771#issuecomment-1021326507
I know, I built it :^)
But it is apparently broken when using `--uidmap=0:11900000:65536 --gidmap=0:11900000:65536` as described in this bug.
The issue is that `catatonit` cannot be copied into the locally built image, yet the image is built - only a log is emitted but it does not error out. When starting the pod, the infra container cannot start (and hence the pod) because `catatonit` is not present in the image.
Comment 19Valentin Rothberg
2022-05-12 09:36:29 UTC
Until a fix is shipped, I suggest using the infra image with Podman v4.0 again.
You can either use `--infra-image=k8s.gcr.io/pause` when creating the pod or configure /etc/containers/containers.conf as follows:
```
[engine]
infra_image = "k8s.gcr.io/pause"
```
Comment 20Valentin Rothberg
2022-05-13 08:11:56 UTC
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: container-tools:rhel8 security, bug fix, and enhancement 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:7457