Bug 1866833
| Summary: | Podman 1.9.3 fails to run container when /etc/secuity/limits.conf is used | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Anthony Hogbin <ahogbin> |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | ajia, bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, tsweeney, ypu |
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | podman-2.0.4 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 03:06:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1186913, 1804543 | ||
|
Description
Anthony Hogbin
2020-08-06 14:10:03 UTC
Giuseppe, can you look at this please? Are they having this on newly created containers? Daniel - I have tested with new - and the issue presents. Yes. This is not specific to their repo or images. Using the steps above it can be recreated. Returning things to as they were and rootless works fine again. Could you look at Fedora and do the same thing, and see if it works in the current release? @Daniel as requested Fedora 32 Server created, and same procedure to recreate. There is no issue as shown below: [ahogbin@fedora32 ~]$ podman run -it registry.access.redhat.com/ubi8/ubi bash Trying to pull registry.access.redhat.com/ubi8/ubi... Getting image source signatures Copying blob 77c58f19bd6e done Copying blob 47db82df7f3f done Copying config a1f8c96997 done Writing manifest to image destination Storing signatures [root@713a6824b04b /]# exit Yum search shows the following podman installed: Name : podman Epoch : 2 Version : 2.0.4 Release : 1.fc32 Architecture : x86_64 Size : 50 M Source : podman-2.0.4-1.fc32.src.rpm This will be fixed in RHEL8.3 podman 2.0.4 or newer. Assigning to Jindrich for any further packaging needs. Jindrich please also change the status of the BZ if necessary. I can reproduce this bug on podman-1.9.3-2.module+el8.2.1+6867+366c07d6.x86_64,
and verified it on podman-2.0.2-2.module+el8.3.0+7374+9d949f97.x86_64
and podman-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64.
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ rpm -q podman
podman-1.9.3-2.module+el8.2.1+6867+366c07d6.x86_64
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ podman unshare cat /proc/self/uid_map
0 1001 1
1 165536 65536
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ podman run -it registry.access.redhat.com/ubi8/ubi bash
Error: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:382: setting rlimits for ready process caused: error setting rlimit type 6: invalid argument: OCI runtime error
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ rpm -q podman podman-catatonit
podman-2.0.2-2.module+el8.3.0+7374+9d949f97.x86_64
podman-catatonit-2.0.2-2.module+el8.3.0+7374+9d949f97.x86_64
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ podman unshare cat /proc/self/uid_map
0 1001 1
1 165536 65536
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ podman run -it registry.access.redhat.com/ubi8/ubi bash
Trying to pull registry.access.redhat.com/ubi8/ubi...
Getting image source signatures
Copying blob 77c58f19bd6e done
Copying blob 47db82df7f3f done
Copying config a1f8c96997 done
Writing manifest to image destination
Storing signatures
[root@e1197ca55998 /]#
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ rpm -q podman podman-catatonit
podman-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64
podman-catatonit-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64
[ajia@hpe-dl380pgen8-02-vm-15 ~]$ podman run -it registry.access.redhat.com/ubi8/ubi bash
Trying to pull registry.access.redhat.com/ubi8/ubi...
Getting image source signatures
Copying blob 47db82df7f3f done
Copying blob 77c58f19bd6e done
Copying config a1f8c96997 done
Writing manifest to image destination
Storing signatures
[root@a8e39c253e80 /]#
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-2020:4694 |