Changes

Jump to navigation Jump to search
300 bytes removed ,  17:41, 13 March 2019
+podman
Line 6: Line 6:  
{{Status|ready}}
 
{{Status|ready}}
   −
Currently, vzctl supports CRIU for checkpoint/restore of upstream containers (i.e. when non-OpenVZ kernel is used). Commands <code>vzctl suspend</code> and <code>vzctl restore</code> fully work. Live migration doesn't work yet as it requires support for <code>vzctl suspend {--suspend, --dump, --kill, --restore}</code> which is not yet implemented as it requires a separate daemon to hold the state of a partially checkpointed container (or an ability from criu tool to do that).
+
As of Virtuozzo/OpenVZ 7, CRIU is fully integrated and supported. Older OpenVZ releases used in-kernel checkpoint/restore functionality, now superseded by CRIU.
* [https://openvz.org Project homepage]
+
 
* [http://git.openvz.org/?p=vzctl&a=search&h=HEAD&st=commit&s=CRIU%7Ccriu%7Ccrtools&sr=1 Relevant vzctl git commits]
+
* [https://openvz.org/ OpenVZ]
* [https://openvz.org/Virtuozzo Virtuozzo] is a virtualization and automation solution built on top of OpenVZ.
+
* [https://virtuozzo.com/ Virtuozzo]
    
=== LXC/LXD ===
 
=== LXC/LXD ===
Line 27: Line 27:     
''See also: [[Docker]] C/R''
 
''See also: [[Docker]] C/R''
 +
 +
== Podman ==
 +
{{Status|ready}}
 +
* [https://podman.io/ Project homepage]
 +
* [https://podman.io/blogs/2018/10/10/checkpoint-restore.html Blog entry about adding the support]
    
=== CoreOS Rocket ===
 
=== CoreOS Rocket ===
Line 42: Line 47:     
* Jerome [https://github.com/jpetazzo/critmux did] this some time ago
 
* Jerome [https://github.com/jpetazzo/critmux did] this some time ago
 +
 +
''See also: [[Screen]]''
    
=== Shell ===
 
=== Shell ===
Line 47: Line 54:     
It would be nice to have bash (or other shell) to launch criu with <code>--restore-sibling</code> option and get new kid processes from it. Right now we workaround it with "[[shell jobs]]".
 
It would be nice to have bash (or other shell) to launch criu with <code>--restore-sibling</code> option and get new kid processes from it. Right now we workaround it with "[[shell jobs]]".
 +
 +
''See also: [[Shell jobs]]''
    
== Other ==
 
== Other ==
Line 73: Line 82:  
=== Systemd ===
 
=== Systemd ===
 
{{Status|not started}}
 
{{Status|not started}}
Adrian suggested that
     −
Migrating
+
Adrian suggested that migrating
processes from one system to another works, depending on the process,
+
processes from one system to another works, depending on the process,
pretty good. Migrating a process under systemd's control might be
+
pretty good. Migrating a process under systemd's control might be
possible by just killing the process on the source side but it cannot
+
possible by just killing the process on the source side but it cannot
become a child process of systemd on the destination of the migration
+
become a child process of systemd on the destination of the migration
without systemd knowing how to restore a process and thus making it a
+
without systemd knowing how to restore a process and thus making it a
child process of systemd (--restore-sibling).
+
child process of systemd (--restore-sibling).
    
[[Category:Plans]]
 
[[Category:Plans]]
 
[[Category:Development]]
 
[[Category:Development]]

Navigation menu