On Fri, Aug 03, 2012 at 05:45:40AM -0700, Eric W. Biederman wrote: > The solution is to use user namespaces and to only test ns_capable on the magic reboot path. > > For the 3.7 timeframe that should be a realistic solution. Hmm, that would imply that if LXC wants to allow reboot()/CAP_SYS_BOOT they will be forced to use CLONE_NEWUSER. I was rather looking for a way to allow the container to keep CAP_SYS_BOOT, without also mandating use of user namespaces. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/containers
