From 2f04316c1995fe4b004b1726f7b10bbb35ce774c Mon Sep 17 00:00:00 2001 From: John Johansen Date: Wed, 8 May 2019 05:59:46 +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 c72787f..44a840c 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 a container in conjunction with another [LSM](how-to-setup-a-policy-namespace-for-containers#major-lsms-explained) confining the host. 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 a container in conjunction with another [LSM](how-to-setup-a-policy-namespace-for-containers#major-lsms-explained) confining the host. 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 complications. This guide endeavours to document what is need to be able to successfully use apparmor with containers in an LSM stacking capable kernel.