Valentin Rothberg edb285d176 apparmor: apply default profile at container initialization ... Apply the default AppArmor profile at container initialization to cover all possible code paths (i.e., podman-{start,run}) before executing the runtime. This allows moving most of the logic into pkg/apparmor. Also make the loading and application of the default AppArmor profile versio-indepenent by checking for the `libpod-default-` prefix and over-writing the profile in the run-time spec if needed. The intitial run-time spec of the container differs a bit from the applied one when having started the container, which results in displaying a potentially outdated AppArmor profile when inspecting a container. To fix that, load the container config from the file system if present and use it to display the data. Fixes: #2107 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>		2019-01-09 22:18:11 +01:00
..
apparmor.go	apparmor: apply default profile at container initialization	2019-01-09 22:18:11 +01:00
apparmor_linux.go	apparmor: apply default profile at container initialization	2019-01-09 22:18:11 +01:00
apparmor_linux_template.go	pkg/apparmor: move data under Linux/apparmor buildtags	2018-08-14 14:25:14 +00:00
apparmor_linux_test.go	pkg/apparmor: use a pipe instead of a tmp file	2018-08-14 14:25:14 +00:00
apparmor_unsupported.go	apparmor: apply default profile at container initialization	2019-01-09 22:18:11 +01:00