CRIU and SELinux
summary
Explains how CRIU (Checkpoint/Restore in Userspace) must manage SELinux labels to implement live migration for container runtimes that use SELinux, describing the steps required to fully restore processes with their SELinux context. Discusses why preserving SELinux state is challenging during live migration, notes that CRIU can now migrate processes/containers without losing SELinux information, and requests feedback on any missing implementation parts.
AI-written summary · about
chapters (11)
- 0:00CRIU and SELinux
- 1:04around 2011
- 2:20BuildRequires: libselinux-devel
- 3:20Read /proc/PID/attr/current
- 5:27Build CRIU from source
- 6:49Injected into the process
- 7:07Daemon waiting for commands
- 7:20Removed after usage
- 7:57setsockcreatecon (3)
- 8:38Write /proc/PID/attr/current
- 14:16proc/sys/kernel/ns_last_pid
related talks
39mContainer Live Migration
26mFast and Service-preserving Recovery from Malware Infections Using CRIU
44mUsing SELinux with container runtimes
33mFreeze,Investigate,Recover: Unlocking Forensic Container Checkpoint...
15mSELinux
24mUnprivileged CRIU
37mCRI-O: Under the Hood
21mCRI-O: Secure, Performant, and Boring...
