Difference between revisions of "Main Page"

From CRIU
Jump to navigation Jump to search
(→‎Under the hood: fixed formatting)
m
 
(129 intermediate revisions by 14 users not shown)
Line 1: Line 1:
−
Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace.
+
<div style="float: {{{1|right}}}">
 +
{{Download box|left}}
 +
[[Image:4.0.c.jpg|right|340px]]
 +
</div>
 +
__NOTOC__
 +
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.
  
−
== This wiki ==
+
Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a Linux software. It can freeze a running container (or an individual application) and checkpoint its state to disk. The data saved can be used to restore the application and run it exactly as it was during the time of the freeze. Using this functionality, application or container live migration, snapshots, remote debugging, and [[usage scenarios|many other things]] are now possible.
 +
 
 +
CRIU started as a project of Virtuozzo, and grew with the tremendous help from the [[community]]. It is currently used by (integrated into) OpenVZ, [[LXC]]/LXD, [[Docker]], [[Podman]], and [[Integration|other software]], and [[packages|packaged for many Linux distributions]].
 +
</big>
 +
{{Like}}
 +
<br clear="both">
 +
 
 +
<div class="m_right">
 +
{{News block 2}}
 +
</div>
 +
 
 +
<div class="m_left">
 +
== Using ==
 +
 
 +
<big>
 +
;Getting [[packages]] for your distribution
 +
: Or try manual [[installation]] to have CRIU on your system
 +
</big>
 +
 
 +
;[[CLI]], [[RPC]] and [[C API]]
 +
: Three ways to start using the C/R functionality.  [[:Category:API|More info]] about APIs.
  
 
;[[Usage scenarios]]
 
;[[Usage scenarios]]
−
: Ideas how crtools can be used (some are crazy indeed)
+
: 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.
 +
 
 +
;[https://www.criu.org/index.php?title=FAQ 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
  
−
;[[CR_tools | CR tools]]
+
</div>
−
: Main checkpoint/restore utility
 
  
−
;[[ZDTM_Test_Suite | ZDTM]]
+
<div class="m_center">
 +
== 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
 
: Zero downtime test suite
  
−
;[[Todo | TODO]]
+
;[[Todo|TODO]]
 
: Current TODO list
 
: Current TODO list
  
−
;[[What software is supported]]
+
;[[User namespace]]
−
: Describes TODO list in higher level terms
+
: Implementing user namespace support
  
−
;[[Commits | Commits]]
+
;[[Postulates]]
−
: Mainline kernel commits tracker
+
: What to keep in mind when writing new code
 +
 
 +
;[https://coveralls.io/github/checkpoint-restore/criu Code coverage results]
 +
: Shows how zdtm run covers the criu code paths
 +
 
 +
;[[How to submit patches]]
 +
:
 +
 
 +
</div>
 +
 
 +
<br clear="both">
 +
<div class="m_left">
 +
== Under the hood ==
 +
* [[Checkpoint/Restore]]
 +
* [[:Category:Under the hood]]
 +
* [[:Category:Network]]
 +
* [[:Category:Files]]
 +
* [[:Category:Memory]]
 +
* [[Pending signals]]
 +
* [[Stages of restoring]]
 +
* [[Code blobs]]
 +
* [[Comparison to other CR projects]]
 +
</div>
  
 +
<div class="m_center">
 
== External links ==
 
== External links ==
 
{{:Articles}}
 
{{:Articles}}
 +
</div>
  
−
== Under the hood ==
+
<div class="m_right">
−
 
+
== Misc ==
−
* [[Sockets]]
+
* [[Academic Research]]
−
* [[Memory dumping and restoring]]
+
* [[Podcasts]] and other audio/video interviews
−
* [[Checkpoint/Restore]]
+
* Project [[history]]
−
* [[TCP connection]]
+
* [[Logo]] description
−
* [[Porting crtools to new kernel releases]]
+
* [[Events]]
 +
* [[CRIU acronym fun]]
 +
</div>

Latest revision as of 14:12, 2 October 2024

Download
Tarball: criu-4.0.tar.gz
Version: 4.0 "CRIUDA"
Released: 20 Sep 2024
GIT tag: v4.0
Installation • Usage
Releases
4.0.c.jpg

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 Linux software. It can freeze a running container (or an individual application) and checkpoint its state to disk. The data saved can be used to restore the application and run it exactly as it was during the time of the freeze. Using this functionality, application or container live migration, snapshots, remote debugging, and many other things are now possible.

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


Events
Feed-icon.svg RSS • Atom


LinuxDays 2024

Linux-days-cz.svg

13 Oct 2024, On the Edge of Tomorrow: Checkpoint/Restore in Containers


Kubernetes Community Days Austria

Kcd-austria.svg

09 Oct 2024, Forensic container checkpointing and analysis


Linux Plumbers Conference 2024

Linuxplumbers.png

18-20 Sep 2024, Containers and Checkpoint/Restore Microconference 

Other talks:
* Userspace memory persistence over kexec
* Checkpoint/Restore In eBPF (CRIB)



More events… – Past events…

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


Under the hood

External links

More external articles...

Misc

Retrieved from "https://criu.org/index.php?title=Main_Page&oldid=5532"