Bug 2066138
| Summary: | failed to open /dev/fuse: Operation not permitted | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Alex Jia <ajia> |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | Alex Jia <ajia> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.7 | CC: | bbaude, ddarrah, dwalsh, gscrivan, jligon, jnovy, lsm5, mbearer, mheon, pthomas, tsweeney, umohnani, ypu |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2057243 | Environment: | |
| Last Closed: | 2023-11-14 15:27:28 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: | |||
|
Comment 3
Alex Jia
2022-03-22 12:16:45 UTC
This is not working on Fedora either. I am not sure what is going wrong. Giuseppe any ideas? Fixed upstream with d2f77c256836e8a1a562d56eed7d92fdb18a2f76 (In reply to Giuseppe Scrivano from comment #5) > Fixed upstream with d2f77c256836e8a1a562d56eed7d92fdb18a2f76 This patch works well for me on RHEL-8.6. [root@kvm-06-guest34 podman]# git show d2f77c25 --no-patch commit d2f77c256836e8a1a562d56eed7d92fdb18a2f76 Author: Hironori Shiina <shiina.hironori.com> Date: Thu Mar 3 21:39:14 2022 -0500 Set default rule at the head of device configuration The default rule should be set at the head of device configuration. Otherwise, rules for user devices are overridden by the default rule so that any access to the user devices are denied. Signed-off-by: Hironori Shiina <shiina.hironori.com> [root@kvm-06-guest34 podman]# ./bin/podman run --rm --device /dev/fuse -it registry-proxy.engineering.redhat.com/rh-osbs/rhel8-buildah:8.6-5 [root@7779acb7d81c /]# rpm -q buildah fuse-overlayfs buildah-1.24.2-2.module+el8.6.0+14488+6524fb7f.x86_64 fuse-overlayfs-1.8.2-1.module+el8.6.0+14488+6524fb7f.x86_64 [root@7779acb7d81c /]# buildah from registry.access.redhat.com/ubi8 Trying to pull registry.access.redhat.com/ubi8:latest... Getting image source signatures Checking if image destination supports signatures Copying blob 3de00bb8554b done Copying blob c530010fb61c done Copying config 552ac8ae42 done Writing manifest to image destination Storing signatures ubi8-working-container [root@7779acb7d81c /]# buildah ps CONTAINER ID BUILDER IMAGE ID IMAGE NAME CONTAINER NAME e05ba45ab055 * 552ac8ae4291 registry.access.redhat.com/ub... ubi8-working-container [root@7779acb7d81c /]# buildah run --isolation=chroot ubi8-working-container ls bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var (In reply to Alex Jia from comment #6) > (In reply to Giuseppe Scrivano from comment #5) > > Fixed upstream with d2f77c256836e8a1a562d56eed7d92fdb18a2f76 > > This patch works well for me on RHEL-8.6. > s/RHEL-8.6/RHEL-8.7/ Assigning to @jnovy for any further BZ or packaging needs. This fix will be present in 8.7.0 in the next release of podman. This bug has been verified on podman-4.0.3-1.module+el8.7.0+14675+ab3d5383. [root@hpe-dl380pgen8-02-vm-14 ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.7 Beta (Ootpa) [root@hpe-dl380pgen8-02-vm-14 ~]# rpm -q podman runc systemd kernel podman-4.0.3-1.module+el8.7.0+14675+ab3d5383.x86_64 runc-1.0.3-3.module+el8.7.0+14675+ab3d5383.x86_64 systemd-239-58.el8.x86_64 kernel-4.18.0-375.el8.x86_64 [root@hpe-dl380pgen8-02-vm-14 ~]# podman run --rm --device /dev/fuse -it registry-proxy.engineering.redhat.com/rh-osbs/rhel8-buildah:8.6-6 Trying to pull registry-proxy.engineering.redhat.com/rh-osbs/rhel8-buildah:8.6-6... Getting image source signatures Copying blob 9a58214aa887 done Copying blob 01ce70940a94 done Copying blob 1aed92981855 done Copying config e13113c970 done Writing manifest to image destination Storing signatures [root@8b0937255fed /]# rpm -q buildah fuse-overlayfs buildah-1.24.2-2.module+el8.6.0+14488+6524fb7f.x86_64 fuse-overlayfs-1.8.2-1.module+el8.6.0+14488+6524fb7f.x86_64 [root@8b0937255fed /]# buildah from registry.access.redhat.com/ubi8 Trying to pull registry.access.redhat.com/ubi8:latest... Getting image source signatures Checking if image destination supports signatures Copying blob 4eef1fa1f1c1 done Copying blob eb24191cef20 done Copying config c54243b588 done Writing manifest to image destination Storing signatures ubi8-working-container [root@8b0937255fed /]# buildah ps CONTAINER ID BUILDER IMAGE ID IMAGE NAME CONTAINER NAME dcf34bfd5fdf * c54243b58814 registry.access.redhat.com/ub... ubi8-working-container [root@8b0937255fed /]# buildah run --isolation=chroot ubi8-working-container ls bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var [root@8b0937255fed /]# exit exit [root@hpe-dl380pgen8-02-vm-14 ~]# echo $? 0 @jnovy can this be closed? Not yet, this waits to be released with 8.7.0. 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 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-2023:6939 |