From 735b734aa1fb6fd5c3f417dd72befdf03603aaec Mon Sep 17 00:00:00 2001 From: John Johansen Date: Thu, 9 May 2019 07:27:04 +0000 Subject: [PATCH] Update how to setup a policy namespace for containers --- how-to-setup-a-policy-namespace-for-containers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/how-to-setup-a-policy-namespace-for-containers.md b/how-to-setup-a-policy-namespace-for-containers.md index f9d78b8..4eb4261 100644 --- a/how-to-setup-a-policy-namespace-for-containers.md +++ b/how-to-setup-a-policy-namespace-for-containers.md @@ -23,9 +23,9 @@ The basic descriptions assume the AppArmor userspace is installed on the host, w 1. [Create an apparmor namespace](how-to-setup-a-policy-namespace-for-containers#creating-an-apparmor-namespace) 2. [Switch the display LSM and put root container task into the apparmor namespace.](how-to-setup-a-policy-namespace-for-containers#starting-the-container-in-the-policy-namespace) - AppArmor 2: ```lsm-exec -l apparmor ; aa-exec -p ":$(NS_NAME):unconfined" -- $(CONTAINER_CMD)``` + AppArmor 2.x: ```lsm-exec -l apparmor ; aa-exec -p ":$(NS_NAME):unconfined" -- $(CONTAINER_CMD)``` - AppArmor 3: ```aa-exec --setlsm -p ":$(NS_NAME):unconfined" -- $(CONTAINER_CMD)``` + AppArmor 3.x: ```aa-exec --setlsm -p ":$(NS_NAME):unconfined" -- $(CONTAINER_CMD)``` ## snappy