From 4baf6d4d5289656580a30f24b1ca2dffd3e9c256 Mon Sep 17 00:00:00 2001 From: PingWang Date: Wed, 13 Feb 2019 18:11:04 +0800 Subject: [PATCH] Update links of apparmor doc (#12593) Signed-off-by: PingWang --- content/en/docs/tutorials/clusters/apparmor.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tutorials/clusters/apparmor.md b/content/en/docs/tutorials/clusters/apparmor.md index 34d85179fb..bfb453b226 100644 --- a/content/en/docs/tutorials/clusters/apparmor.md +++ b/content/en/docs/tutorials/clusters/apparmor.md @@ -390,7 +390,7 @@ Pod is running. To debug problems with AppArmor, you can check the system logs to see what, specifically, was denied. AppArmor logs verbose messages to `dmesg`, and errors can usually be found in the system logs or through `journalctl`. More information is provided in -[AppArmor failures](http://wiki.apparmor.net/index.php/AppArmor_Failures). +[AppArmor failures](https://gitlab.com/apparmor/apparmor/wikis/AppArmor_Failures). ## API Reference @@ -414,7 +414,7 @@ Specifying the profile a container will run with: containers, and unconfined (no profile) for privileged containers. - `localhost/`: Refers to a profile loaded on the node (localhost) by name. - The possible profile names are detailed in the - [core policy reference](http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Profile_names_and_attachment_specifications). + [core policy reference](https://gitlab.com/apparmor/apparmor/wikis/AppArmor_Core_Policy_Reference#profile-names-and-attachment-specifications). - `unconfined`: This effectively disables AppArmor on the container. Any other profile reference format is invalid.