Skip to content
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

Enable security.nesting by default for unprivileged containers and modern enough images #13631

Open
mihalicyn opened this issue Jun 17, 2024 · 2 comments
Labels
Maybe Undecided whether in scope for the project

Comments

@mihalicyn
Copy link
Member

I believe we have no choice and should set security.nesting=true (unprivileged case only) for modern enough images (e.g. starting from Oracular [1]).
This depends on a systemd version, not really a distro-specific thing.

For privileged containers, problem even more serious [2] as these days Noble doesn't work in a privileged container. And only works with nesting enabled which makes a container escapable.

See also:
[1] #12698
[2] #12967

@simondeziel
Copy link
Member

I believe we have no choice and should set security.nesting=true (unprivileged case only) for modern enough images.

From a security point of view, is it more dangerous to have nesting enabled if the (unprivileged) container is Jammy or Oracular?

If the answer is no, I think we should discuss whether we always enable security.nesting for unprivileged containers as even Noble and earlier releases have diverse issues with systemd units using namespace features.

@tomponline tomponline added the Maybe Undecided whether in scope for the project label Jun 18, 2024
@tomponline
Copy link
Member

Seems relevant lxc/incus#650

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maybe Undecided whether in scope for the project
Projects
None yet
Development

No branches or pull requests

3 participants