Closed snprajwal closed 1 year ago
0 tests - 24 0 :heavy_check_mark: - 24 0s :stopwatch: ±0s 0 suites - 1 0 :zzz: ± 0 0 files - 1 0 :x: ± 0
Results for commit 505fc539. ± Comparison against base commit c3bcdc6b.
Looks like GitHub runners don't support checkpointing with podman. The workflows throw an error for podman container checkpoint
saying configured runtime does not support checkpoint/restore
. We might have to use an external bare metal runner or a VM for this (maybe the CirrusCI instances we use with CRIU?)
Looks like GitHub runners don't support checkpointing with podman. The workflows throw an error for
podman container checkpoint
sayingconfigured runtime does not support checkpoint/restore
. We might have to use an external bare metal runner or a VM for this (maybe the CirrusCI instances we use with CRIU?)
The version of crun probably has not been compiled with CRIU support. Just switching to runc should already fix this.
Using runc lets us checkpoint, but the stats-dump
file is missing for some reason. Not sure why. The logs are available here: https://github.com/snprajwal/checkpointctl/actions/runs/5477217792/jobs/9975920598#step:6:50
I am also passing -k
to preserve CRIU statistics files, but that didn't change the output.
Maybe the Podman version is too old. We added support for statistics not from the beginning.
This currently fails because I'm doing some container inception (trying to checkpoint a podman container running on a Fedora container in GH Actions). Not sure why CRIU is failing, and podman doesn't provide a verbose flag to log info about the checkpointing process.
Fixes #68