What cannot be checkpointed
This article describes what application can do to make CRIU refuse to dump it, summarizing our experience in the area.
Note that there is no "What cannot be restored" article, and never will be. Is something was dumped, it should be restored.
- 1 External resources
- 2 File locks
- 3 Devices
- 4 Tasks with debugger attached
- 5 Task from a different user (for non-root)
- 6 Task running in compat mode (x86-64)
- 7 UNIX sockets with relative path
- 8 Btrfs
- 9 TimerFD
- 10 Sockets other than TCP, UDP, UNIX, packet and netlink
- 11 Packetized pipes
- 12 Cork-ed UDP sockets
- 13 SysVIPC memory segment w/o IPC namespace
By default CRIU allows to dump the set of processes and their resources if this set has no connections outside. However, in some situations it makes sense to ignore this external connection on dump and recreate one on restore. So, what this "connection outside" is? For example:
- UNIX socket. Application may have a UNIX socket connected to some other app and the latter one is not dumped. This is called external UNIX socket.
- TTY, group and session. If you start a program from shell, the tty, process group and session of the new program can be shared with the shell itself. People often meet this when they try CRIU for the first tome on a simple loop.
- TCP connection. This socket is literally an external connection, so CRIU should be explicitly allowed to dump one.
A file lock is an object, that belongs to some filesystem. On dump it's impossible to find out whether this lock help by one task can be used by some other. Thus, CRIU doesn't dump tasks with held locks. The
--file-locks CLI option tells CRIU to dump the lock.
If a task has opened or mapped any character or block device, this typically means, it wants some connection to the hardware. In this case dump (and restore) is impossible. The exception is virtual devices like null, zero, etc. and TUN network device (used by OpenVPN).
The explanation why device file cannot be dumped and restored in a generic way is two fold. First of all, application can be dumped for live migration and on restore there can be no such device. But that's easy. Other than this, we don't know how all the devices work. App might have loaded some state into it, and in order to dump it properly we need to fetch that state. This is not something that can be done in a generic manner.
Tasks with debugger attached
CRIU uses the same API as debuggers do to get some tasks' state and this API (the ptrace one) doesn't allow for multiple debuggers to explore a task. Thus tasks under gdb or strace cannot be dumped.
Task from a different user (for non-root)
For security reasons, if CRIU is requested by non-root to dump some other task, it doesn't do it unless the dumpee belongs to the same user.
Task running in compat mode (x86-64)
We don't yet support 32 bit tasks. Though it should be fixed with time.
UNIX sockets with relative path
For bound unix sockets kernel only provides the path with this the bind() syscall was called. If the path is relative we have no reliable way to find the exact socket location out and just refuse to dump the task.
At the moment we are experiencing problems with files on Btrfs. We hope to fix it soon though.
These are pipes created with
Cork-ed UDP sockets
SysVIPC memory segment w/o IPC namespace
IPC objects are not tied to any tasks. Thus once CRIU meets an IPC memory attached to a task, it requires the whole IPC namespace to be dumped as well.