-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spec: simplify handling of --ulimit host #3583
spec: simplify handling of --ulimit host #3583
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I'm always in favor of simplification... LGTM, but your tests are red |
64fea3c
to
1313aa1
Compare
LGTM |
1313aa1
to
f68a2a6
Compare
it seems enough to not specify any ulimit block to maintain the host limits. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
f68a2a6
to
2f0ed53
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@giuseppe, the only diff I found with the hosts limit is the soft limit for open files (host=1024, ctr=524288=hard limit). The behaviour is the same prior to this change.
that happens because we bump immediately the limit in main_local.go. |
/lgtm |
it seems enough to not specify any ulimit block to maintain the host
limits.
Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com