You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
buildah segfaults upon lack of inotify instances.
Note: upon inspection of the stacktrace, I guessed the underlying issue, closed a few applications, launched podman build again and this time it ran flawlessly.
Steps to reproduce the issue:
Get a Linux system where /proc/sys/fs/inotify/max_user_instances is a little low (e.g. on Debian Sid, it seems to be 128) compared to your actual usage (which can be inspected using inotify-info).
Run a buildah/podman build command. You should get the stacktrace below.
Description
buildah segfaults upon lack of inotify instances.
Note: upon inspection of the stacktrace, I guessed the underlying issue, closed a few applications, launched
podman build
again and this time it ran flawlessly.Steps to reproduce the issue:
/proc/sys/fs/inotify/max_user_instances
is a little low (e.g. on Debian Sid, it seems to be 128) compared to your actual usage (which can be inspected using inotify-info).build
command. You should get the stacktrace below.Describe the results you received:
Describe the results you expected:
An error message like "unable to allocate inotify instance" would be nice.
Output of
rpm -q buildah
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: