-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix: set limitnofile #713
fix: set limitnofile #713
Conversation
When we upgraded containerd 1.4 to 1.6, the systemd unit changed the file descriptor limit from |
Looking upstream this seems to be caused by this PR which sets the containerd limits to unlimited, users who were previously on 1.4.13 version of containerd provided by dkp 2.4 and previous had this limit set. Removing this limit caused our rook deployment to break and we also saw problem with HA proxy as well which had this limit as the root cause. We decided to bring this limit back for a couple of reasons
|
bdc833d
to
d5b0c02
Compare
7a75cf5
to
c2559a9
Compare
@faiq I think we are good to merge this, the 2 other fixes look good: |
template: | ||
dest: /etc/systemd/system/containerd.service.d/max-files.conf | ||
src: etc/systemd/system/containerd.service.d/max-files.conf | ||
mode: 0644 |
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.
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.
What problem does this PR solve?:
https://d2iq.atlassian.net/browse/D2IQ-96107
This change in contained seems to cause problems for workloads that use disk containerd/containerd#4475
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: