-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Dockerfile: update runc binary to 1.2.1 #5443
Conversation
This seems to be more complicated. See #5157 |
The dmz stuff is opt-in and is likely going to be removed in v1.2.1 |
Is there a writeup for the dmz/overlay/vanilla solutions? What do they mean and what is the difference security and performance wise? The PR adding dmz to Moby seems to still be open. |
Some benchmark results are available in |
The tl;dr is that Security-wise, all of the options provide the same level of protection in practice (except for the pre-1.2 bindfds, which were not really secure). In theory a DirtyCow-like attack would be able to overwrite the binary with |
Rootless BuildKit (as well as Docker, contained, etc.) executes runc in an existing UserNS, so it should just work? |
Yeah that should work fine on >=5.11 kernels when overlayfs was enabled inside user namespaces. |
https://github.com/opencontainers/runc/releases/tag/v1.2.0 https://github.com/opencontainers/runc/releases/tag/v1.2.1 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
ef07f77
to
d7a533d
Compare
Updated for v1.2.1 |
https://github.com/opencontainers/runc/releases/tag/v1.2.0
https://github.com/opencontainers/runc/releases/tag/v1.2.1