summaryrefslogtreecommitdiff
path: root/pkg/network
diff options
context:
space:
mode:
authorAdrian Reber <areber@redhat.com>2021-11-17 16:55:43 +0000
committerAdrian Reber <areber@redhat.com>2021-11-19 17:46:06 +0000
commitc76caba367583c5d4f1e8fe3f111383148d4d175 (patch)
treed53725f3777e678942b902038cfe1fde42ca07f9 /pkg/network
parent671e5ee42d4eb71fc0238e8b0b1e4a68b1def156 (diff)
downloadpodman-c76caba367583c5d4f1e8fe3f111383148d4d175.tar.gz
podman-c76caba367583c5d4f1e8fe3f111383148d4d175.tar.bz2
podman-c76caba367583c5d4f1e8fe3f111383148d4d175.zip
Use same runtime to restore a container as during checkpointing
There are at least two runtimes that support checkpoint and restore: runc and crun. Although the checkpoints created by these are almost compatible, it is not (yet) possible to restore a checkpoint created with one runtime with the other runtime. To make checkpoint/restore usage more comfortable this adds code to look into the checkpoint archive during restore and to set the runtime to the one used during checkpointing. This also adds a check, if the user explicitly sets a runtime during restore, that the runtime is also the same as used during checkpointing. If a different runtime is selected than the one used during checkpointing the restore will fail early. If runc and crun will create compatible checkpoints in the future the check can be changed to treat crun and runc as compatible checkpoint/restore runtimes. Signed-off-by: Adrian Reber <areber@redhat.com>
Diffstat (limited to 'pkg/network')
0 files changed, 0 insertions, 0 deletions