container features deployment limited to root


Distinguished Member
Oct 16, 2015
Chatsworth, CA
I have recently began deployment of nested containers following an orderly upgrade to 5.3, when I noticed that only a root user may actually flag the features. What is the rationale for this limitation? What are the implications of setting these flags I'm not considering?
What is the rationale for this limitation?

Security. A normal container should not have permissions to do all those things, as this can severely damage the host system (if a bad/untrusted user inside the container tries to hack you).
Thanks @dietmar , I had a gut feeling that this isnt benign just because we are not opening up the apparmor profile. Can you expand a bit more about the relationship of the nested flag and what apparmor is allowing/preventing when it is?


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!