-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.10
-
None
-
None
-
Moderate
-
rhel-container-tools
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
podman exec -it mail4d bash
podman start mail4d
What is the impact of this issue to you?
Could not run commands inside containers or restart containers
Please provide the package NVR for which the bug is seen:
maybe containers-common-2:1-82.module+el8.10.0+23647+cfd78660.x86_64
How reproducible is this bug?:
Steps to reproduce
Expected results
podman actions like following works:
podman exec -it mail4d bash
podman start mail4d
Actual results
podman exec -it mail4d bash
podman start mail4d
failed with
untime stderr: exec failed: unable to start container process: error closing exec fds: get handle to /proc/thread-self/fd: unsafe procfs detected: openat2 /proc/thread-self/fd/: function not implemented
or
runtime stderr: runc create failed: unable to start container process: error during container init: error closing exec fds: get handle to /proc/thread-self/fd: unsafe procfs detected: openat2 /proc/thread-self/fd/: function not implemented
- is duplicated by
-
RHEL-130510 unable to start container process: error closing exec fds: get handle to /proc/thread-self/fd: unsafe procfs detected: openat2 /proc/thread-self/fd/: function not implemented
-
- Closed
-
- links to