Browse files

attach: handle apparmor transitions in !NEWNS cases

If we're not attaching to the mount ns , then don't enter the
container's apparmor policy.  Since we're running binaries from the host
and not the container, that actually seems the sane thing to do (besides
also the lazier thing).

If we dont' do this patch, then we will need to move the apparmor attach
past the procfs remount, will need to also mount securityfs if available,
and for the !remount_proc_sys case we'll want to mount those just long
enough to do the apparmor transition.

Signed-off-by: Serge Hallyn <>
Acked-by: Stéphane Graber <>
  • Loading branch information...
1 parent 53a5409 commit 990d9d7c371d26021f14d25a62484776b1f14d32 Serge Hallyn committed with stgraber Mar 6, 2013
Showing with 5 additions and 3 deletions.
  1. +5 −3 src/lxc/lxc_attach.c
8 src/lxc/lxc_attach.c
@@ -376,9 +376,11 @@ int main(int argc, char *argv[])
- if (attach_apparmor(init_ctx->aa_profile) < 0) {
- ERROR("failed switching apparmor profiles");
- return -1;
+ if ((namespace_flags & CLONE_NEWNS)) {
+ if (attach_apparmor(init_ctx->aa_profile) < 0) {
+ ERROR("failed switching apparmor profiles");
+ return -1;
+ }
/* A description of the purpose of this functionality is

0 comments on commit 990d9d7

Please sign in to comment.