segfault when running with memory limit but without swap limit #9429
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
Explicitly removing swap limit causes a segmentation fault.
Steps to reproduce the issue:
sudo podman run --memory 256m --memory-swap -1 busybox true
Describe the results you received:
panic: runtime error: invalid memory address or nil pointer dereference
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
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?
No
Additional environment details (AWS, VirtualBox, physical, etc.):
Ubuntu 20.04
These are supposed to be equivalent:
System doesn't have "cgroup_enable=memory swapaccount=1" cmdline
The text was updated successfully, but these errors were encountered: