Starting containers fails with message 'open /proc/sys/net/ipv4/ping_group_range : no such file or directory: oci runtime attempted to invoke a command that was not found' #11210
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Trying to create/start containers fails with the error message
open /proc/sys/net/ipv4/ping_group_range : no such file or directory: oci runtime attempted to invoke a command that was not found
This affects both unprivileged users as well as root.
Steps to reproduce the issue:
podman run -ti --rm --log-level trace --name foo ubuntu:20.04
Describe the results you received:
The command fails. Complete trace log:
Describe the results you expected:
An interactive shell session inside the created container.
Additional information you deem important (e.g. issue happens only occasionally):
It worked fine before. Already tried to downgrade the
podman
package itself (first to 3.2.2, then 3.2.1 without success)Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
This is all happening on a physical box.
The text was updated successfully, but these errors were encountered: