Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with podman
Search options not deleted
user 41492
3
votes
Processes in "podman build" have lower file descriptor limit than processes in "podman run",...
podman accept --ulimit=host, which is convenient if you want the same policy, but 3.4.4 does not, and in any case --ulimit=host works only for podman create and podman run. … For podman build specifying limit names is a requirement.
For the file descriptor limit the proper name is nofiles. The
podman documentation for version 4.4 describes additional valid limit names. …
- 161
3
votes
2
answers
1k
views
Processes in "podman build" have lower file descriptor limit than processes in "podman run",...
I'm running podman 3.4.4 on Ubuntu 22.04 LTS server.
I have been having podman build issues that are not reproducible if I do those steps after the container build using podman run. … Update: I'm told there is a --ulimit option to podman, and indeed there is. But podman 3.4.4, which is standard on Ubuntu 22.04, does not support the simple --ulimit=host version. …
- 161