Revert "Temporarily disable CAP_PERFMON, CAP_BPF, and CAP_CHECKPOINT_RESTORE#42011
Conversation
oci/caps/utils.go
Outdated
There was a problem hiding this comment.
This will break dind (Docker 21 in Docker 20.10). I still think containerd/containerd#5017 is the right approach.
There was a problem hiding this comment.
(Might be fine for runc >= rc94, though, as runc >= rc94 does not raise error on unknown caps opencontainers/runc#2854)
480f9f0 to
9f28ade
Compare
|
What's current status? |
9f28ade to
f55ef5f
Compare
I rebased to trigger CI again. I think this one should be fine now that we're on runc > rc94, correct? |
|
Failure is unrelated; |
f55ef5f to
db8282e
Compare
|
hmpf |
8ae145e to
0c87d92
Compare
|
@AkihiroSuda @cpuguy83 PTAL |
|
Failure is unrelated, but looks like that one is flaky as well |
|
Opened #42698 to track that one |
…RESTORE" Now that runc v1.0.0-rc93 is used, we can revert this temporary workaround This reverts commit a38b96b. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
0c87d92 to
c1c973e
Compare
|
Hi, Is there a plan to back port this to stable release? The use case for this has been explained here. |
|
@thaJeztah @cpuguy83 any thoughts on above? |
|
CRIU has merged patches to use CAP_CHECKPOINT_RESTORE in checkpoint-restore/criu#1930. This allows us to build images containing checkpointed processes that can be restored in containers with far fewer privileges and capabilities. The benefits here are much faster startup and reduced time to first response. Podman and others support it, so it would really be nice to have Docker support in stable releases finally. |
fixes #42601
Revert "Temporarily disable CAP_PERFMON, CAP_BPF, and CAP_CHECKPOINT_RESTORE"
Now that runc v1.0.0-rc93 is used, we can revert this temporary workaround
This reverts commit a38b96b (#41563).
relates to:
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)