Difference between revisions of "Main Page"
Jump to navigation
Jump to search
| (36 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
| − | {{Download box| | + | <div style="float: {{{1|right}}}"> |
| + | {{Download box|left}} | ||
| + | [[Image:Willet_texas_april2003_1_1280.png|right|178px]] | ||
| + | </div> | ||
__NOTOC__ | __NOTOC__ | ||
| − | <big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux | + | <big>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 | + | 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}} | {{Like}} | ||
<br clear="both"> | <br clear="both"> | ||
| − | <div | + | <div class="m_right"> |
| + | {{News block 2}} | ||
| + | </div> | ||
| + | <div class="m_left"> | ||
== Using == | == Using == | ||
| Line 19: | Line 25: | ||
</big> | </big> | ||
| − | ;[[ | + | ;[[CLI]], [[RPC]] and [[C API]] |
| − | : Three ways to start using the C/R functionality | + | : Three ways to start using the C/R functionality. [[:Category:API|More info]] about APIs. |
;[[Usage scenarios]] | ;[[Usage scenarios]] | ||
| Line 28: | Line 34: | ||
: 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. | : 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 | : A sort of troubleshooting guide | ||
| Line 39: | Line 42: | ||
;[[What cannot be checkpointed]] | ;[[What cannot be checkpointed]] | ||
: What an application could do to make CRIU refuse to dump it. | : What an application could do to make CRIU refuse to dump it. | ||
| + | |||
| + | ;[[Contacts]] | ||
| + | : Ways to communicate with CRIU community | ||
</div> | </div> | ||
| − | <div | + | <div class="m_center"> |
== Developing == | == Developing == | ||
| − | If you're interested in CRIU development, please subscribe to the criu mailing list: | + | If you're interested in CRIU development, please subscribe to the criu mailing list: https://lists.openvz.org/mailman/listinfo/criu |
;[[Images]] | ;[[Images]] | ||
| Line 67: | Line 73: | ||
: Current TODO list | : Current TODO list | ||
| − | ;[[ | + | ;[[User namespace]] |
: Implementing user namespace support | : Implementing user namespace support | ||
| Line 73: | Line 79: | ||
: What to keep in mind when writing new code | : 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 | : Shows how zdtm run covers the criu code paths | ||
| Line 79: | Line 85: | ||
: | : | ||
| − | |||
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
<br clear="both"> | <br clear="both"> | ||
| − | <div | + | <div class="m_left"> |
| − | == | + | == Under the hood == |
| − | |||
| − | |||
* [[Checkpoint/Restore]] | * [[Checkpoint/Restore]] | ||
| − | * [[ | + | * [[:Category:Under the hood]] |
| − | * [[Files]] | + | * [[:Category:Network]] |
| + | * [[:Category:Files]] | ||
| + | * [[:Category:Memory]] | ||
* [[Pending signals]] | * [[Pending signals]] | ||
* [[Stages of restoring]] | * [[Stages of restoring]] | ||
| − | |||
* [[Code blobs]] | * [[Code blobs]] | ||
* [[Comparison to other CR projects]] | * [[Comparison to other CR projects]] | ||
| − | |||
</div> | </div> | ||
| − | <div | + | <div class="m_center"> |
== External links == | == External links == | ||
{{:Articles}} | {{:Articles}} | ||
</div> | </div> | ||
| − | <div | + | <div class="m_right"> |
| − | == | + | == Misc == |
| + | * [[Podcasts]] and other audio/video interviews | ||
* Project [[history]] | * Project [[history]] | ||
* [[Logo]] description | * [[Logo]] description | ||
* [[Events]] | * [[Events]] | ||
| − | * | + | * [[CRIU acronym fun]] |
</div> | </div> | ||
Revision as of 08:14, 29 January 2020
|
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.
|
Using
- Getting packages for your distribution
- Or try manual installation to have CRIU on your system
- 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
Under the hood
External links
- 2024-04-22, Pronghorn: Effective Checkpoint Orchestration for Serverless Hot-Starts
- 2023-11-12, Checkpoint/Restart for CUDA Kernels
- 2023-10-23, Evicting for the greater good: The Case for Reactive Checkpointing in Serverless Computing
- 2023-04-20, A Dynamic Checkpoint Interval Decision Algorithm for Live Migration-Based Drone-Recovery System
- 2023-03-10, Forensic Container Analysis
- 2023-01-14, Async-fork: Mitigating Query Latency Spikes Incurred by the Fork-based Snapshot Mechanism from the OS Level
- 2022-12-05, Forensic container checkpointing in Kubernetes
- 2022-11-13, Out of hypervisor (OoH): efficient dirty page tracking in userspace using hardware virtualization feature
- 2022-08-07, iContainer: Consecutive Checkpointing with Rapid Resilience for Immortal Container-based Services
Misc
- Podcasts and other audio/video interviews
- Project history
- Logo description
- Events
- CRIU acronym fun