Update links of apparmor doc (#12593)

Signed-off-by: PingWang <wang.ping5@zte.com.cn>
This commit is contained in:
PingWang
2019-02-13 18:11:04 +08:00
committed by Kubernetes Prow Robot
parent 1bfe9725f9
commit 4baf6d4d52
@@ -390,7 +390,7 @@ Pod is running.
To debug problems with AppArmor, you can check the system logs to see what, specifically, was 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 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 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 ## API Reference
@@ -414,7 +414,7 @@ Specifying the profile a container will run with:
containers, and unconfined (no profile) for privileged containers. containers, and unconfined (no profile) for privileged containers.
- `localhost/<profile_name>`: Refers to a profile loaded on the node (localhost) by name. - `localhost/<profile_name>`: Refers to a profile loaded on the node (localhost) by name.
- The possible profile names are detailed in the - 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. - `unconfined`: This effectively disables AppArmor on the container.
Any other profile reference format is invalid. Any other profile reference format is invalid.