From e772e3d1b43541ec067870a0f24e2b168894249e Mon Sep 17 00:00:00 2001 From: John Johansen Date: Mon, 6 May 2019 08:58:32 +0000 Subject: [PATCH] Update how to setup a policy namespace for containers --- how-to-setup-a-policy-namespace-for-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-to-setup-a-policy-namespace-for-containers.md b/how-to-setup-a-policy-namespace-for-containers.md index 1e5043b..99ebf4d 100644 --- a/how-to-setup-a-policy-namespace-for-containers.md +++ b/how-to-setup-a-policy-namespace-for-containers.md @@ -1,6 +1,6 @@ # Intro -With LSM stacking it is possible to use apparmor in conjunction with another [major LSM](how-to-setup-a-policy-namespace-for-containers#major-lsms-explained). Unfortunately it is not entirely straight forward to do so and because LSM stacking support and support for namespacing an LSM have landed piecemeal there are many complication. This guide endeavours to document what is need to be able to successfully use apparmor with containers in an LSM stacking capable kernel. +With LSM stacking it is possible to use apparmor in conjunction with another [LSM](how-to-setup-a-policy-namespace-for-containers#major-lsms-explained). Unfortunately it is not entirely straight forward to do so and because LSM stacking support and support for namespacing an LSM have landed piecemeal there are many complication. This guide endeavours to document what is need to be able to successfully use apparmor with containers in an LSM stacking capable kernel.