0d22571519
The `apparmor_parser` binary is not really required for a system to run AppArmor from a Kubernetes perspective. How to apply the profile is more in the responsibility of lower level runtimes like CRI-O and containerd, which may do the binary check on their own. This synchronizes the current libcontainer implementation with the vendored Kubernetes source code and allows distributions to use AppArmor, even when they do not have the parser available in `/sbin/apparmor_parser`. Signed-off-by: Sascha Grunert <mail@saschagrunert.de> |
||
|---|---|---|
| .. | ||
| apparmor | ||
| podsecuritypolicy | ||
| doc.go | ||