Main Page

Revision as of 11:42, 6 November 2018 by Xemul (talk | contribs) (Added 311 artwork on the main page)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Tarball: criu-3.11.tar.bz2
Version: 3.11 "Glass Flamingo"
Released: 06 Nov 2018
GIT tag: v3.11
ReleasesRelease schedule

Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for the Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it as a collection of files on disk. You can then use the files to restore the application and run it exactly as it was during the time of the freeze. With this feature, application live migration, snapshots, remote debugging, and many other things are possible.

CRIU started as a project of Virtuozzo and grew with tremendous help from the community. It is currently used by (integrated into) OpenVZ, LXC/LXD, Docker, and other software, and CRIU packages is included into many Linux distributions.

Feed-icon.svg RSSAtom

Serverless meetup 2018


Oct 18, 2018, Moscow

Задержки при вызове serverless функций: как формируются, на что влияют и как ими управлять, Владимир Порохов, Swifty Cloud

--User:Xemul 11:55, 17 October 2018 (UTC)

Open Source Summit Europe 2018


Oct 24, 2018, Edinburgh, UK

To Kill, or to Checkpoint - That is the Question

--User:Adrian 09:46, 29 September 2018 (UTC)

Linux Plumbers Conference 2018


Nov 13-15, 2018, Vancouver, Canada

Containers and Checkpoint-Restart microconf

--User:Rppt 18:32, 13 Aug 2018 (IDT)


Getting packages for your distribution
Or try manual installation to have CRIU on your system

Three ways to start using the C/R functionality. More info about APIs.
Usage scenarios
Ideas how criu can be used (some are crazy indeed)
Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a simple loop might be the best one to start with. Also a set of asciinema records for real-life examples.
FAQ & When C/R fails
A sort of troubleshooting guide
What can change after C/R
CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.
What cannot be checkpointed
What an application could do to make CRIU refuse to dump it.
Ways to communicate with CRIU community


If you're interested in CRIU development, please subscribe to the criu mailing list:

Description of image files format
CRIU can call plugins provided by people
Upstream kernel commits
Mainline kernel commits tracker
Recent commits
CRIU tool repository commits
Kernel's manpages commits tracker
ZDTM Test Suite
Zero downtime test suite
Current TODO list
User namespace
Implementing user namespace support
What to keep in mind when writing new code
Code coverage results
Shows how zdtm run covers the criu code paths
How to submit patches