containers
/
podman
mirror of https://github.com/containers/podman.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
podman/pkg/sysinfo
History
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
..
README.md Update vendor of runc 2019-01-04 14:54:59 -05:00
numcpu.go Update vendor of runc 2019-01-04 14:54:59 -05:00
numcpu_linux.go Update vendor of runc 2019-01-04 14:54:59 -05:00
numcpu_windows.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_linux.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_linux_test.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_solaris.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_test.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_unix.go Update vendor of runc 2019-01-04 14:54:59 -05:00
sysinfo_windows.go Update vendor of runc 2019-01-04 14:54:59 -05:00

README.md

SysInfo stores information about which features a kernel supports.