Closed MartinEmrich closed 8 months ago
This is fixed in podman 5.0
@rhatdan thanks!
For anyone finding this: Until that is released, this wrapper (earlier in the $PATH) works ok for me:
#!/bin/bash
REAL_PODMAN=/usr/bin/podman
if [[ "$*" =~ "build " ]]; then
shift
exec ${REAL_PODMAN} build --ulimit=nofile=1048576:1048576 "$@"
fi
exec ${REAL_PODMAN} "$@"
Issue Description
The maximum number of open files does not match between
podman run
andpodman build
I am running "rootless", Podman 4.3.1.
On my System, I get max open files of 1M (Debian 12 on WSL2, default settings):
With
podman run
, I also get enough:But with
podman build
, I only geht 1024, and I see no reason why:The
--ulimit
command line option is not a solution. I have a symlink fromdocker
in my path and run build scripts from third parties, which I cannot modify easily.Steps to reproduce the issue
Steps to reproduce the issue:
Oneliner to visualize:
Describe the results you received
Severely limited nofile ulimit value (and possibly others?)
Describe the results you expected
Exactly the ulimits my calling shell currently has, or at least the same behaviour as
podman run
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
No response
Additional information
ulimit -n 1048576
has no effect.