Main Page

From CRIU
Revision as of 19:19, 27 November 2017 by Avagin (talk | contribs) (Fix the coerall.io link)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Download
Tarball: criu-3.6.tar.bz2
Version: 3.6 "Alabaster Finch"
Released: 23 Oct 2017
GIT tag: v3.6
InstallationUsage
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.


Events
Feed-icon.svg RSSAtom

Open Source Summit EU 2017

Osseu17.png

Oct 23, 2017, Prague, Czech Republic

Mike Rapoport and Adrian Reber will will talk about live migration

--User:Xemul 12:00, 23 Aug 2017 (MSK)

SECR 2017

Secr17logo.png

Oct 20, 2017, St. Petersburg, Russia

Pavel Begunkov will talk about file locks checkpoint and restore.

--User:Xemul 13:30, 12 Sep 2017 (MSK)


Using

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

CLI, RPC and C API
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)
Category:HOWTO
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.
Contacts
Ways to communicate with CRIU community

Developing

If you're interested in CRIU development, please subscribe to the criu mailing list: https://lists.openvz.org/mailman/listinfo/criu

Images
Description of image files format
Plugins
CRIU can call plugins provided by people
Upstream kernel commits
Mainline kernel commits tracker
Recent commits
CRIU tool repository commits
Manpages
Kernel's manpages commits tracker
ZDTM Test Suite
Zero downtime test suite
TODO
Current TODO list
User namespace
Implementing user namespace support
Postulates
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


Misc