Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Fix unconfined AppArmor profile usage for unsupported systems | Sascha Grunert | 2020-09-07 |
| | | | | | | | | If we select "unconfined" as AppArmor profile, then we should not error even if the host does not support it at all. This behavior has been fixed and a corresponding e2e test has been added as well. Signed-off-by: Sascha Grunert <sgrunert@suse.com> | ||
* | Switch all references to github.com/containers/libpod -> podman | Daniel J Walsh | 2020-07-28 |
| | | | | Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> | ||
* | Support default profile for apparmor | Daniel J Walsh | 2020-07-22 |
Currently you can not apply an ApparmorProfile if you specify --privileged. This patch will allow both to be specified simultaniosly. By default Apparmor should be disabled if the user specifies --privileged, but if the user specifies --security apparmor:PROFILE, with --privileged, we should do both. Added e2e run_apparmor_test.go Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> |