Fix setting swaplimit=true without checking memory.swap.max#42071
Fix setting swaplimit=true without checking memory.swap.max#42071thaJeztah merged 1 commit intomoby:masterfrom
Conversation
|
cc @AkihiroSuda as issue author |
99872ec to
b7c01c1
Compare
b7c01c1 to
c5e1235
Compare
AkihiroSuda
left a comment
There was a problem hiding this comment.
Thanks, but we need to support dind case (g="/", in a cgroup namespace)
c5e1235 to
7c7b50d
Compare
|
I feel ci problems are not related to this issue, but anyway, rebase? |
|
restarted CI |
7c7b50d to
09ffefd
Compare
|
@thaJeztah @AkihiroSuda how the situation looks like with this change? CI failures are unrelated. |
|
@thaJeztah PTAL? |
09ffefd to
eded8e4
Compare
|
s390x failures are unrelated. |
|
CI seems to have to be green 😞 @thaJeztah Can we relax "Merging is blocked" restriction? |
|
@jmguzik Could you rebase? It will perhaps make Ci green. |
Signed-off-by: Jakub Guzik <[email protected]>
eded8e4 to
7ef6ece
Compare
|
I kicked CI Failures:
|
|
All green, except for the |
|
Cherry-pick: #42479 |
- What I did
fixes #41926
- How I did it
Added one condition to moby/pkg/sysinfo/cgroup2_linux.go
- How to verify it
Actually, I wanted to create unit tests for this one. The problem is certain files must be present on FS, so I see 2 solutions:
I do not know what is the common practice in the project (1st PR), so I decided just to simply open a PR and ask.
- Description for the changelog
Fixes setting swaplimit=true without checking memory.swap.max
- A picture of a cute animal (not mandatory but encouraged)
Another time :)