Description of problem: When we do checkpoint with file lock inside container but without --file-locks flag, criu can not report error as expected. Version-Release number of selected component (if applicable): criu-3.15-13.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. start a container with a file lock inside # podman run -it --security-opt seccomp=unconfined -d --ip 10.88.158.133 --name test_name quay.io/libpod/alpine:latest flock test.lock sleep 100 e4bd6118abf9b1ef0cfaf3bb4c94e7e7d0c961e5635e4eec1d77d3427e446932 2. make a checkpoint without --file-locks # podman container checkpoint test_name e4bd6118abf9b1ef0cfaf3bb4c94e7e7d0c961e5635e4eec1d77d3427e446932 Actual results: checkpoint can be made successfully Expected results: An error message should be raise to remind user to check the dump.log and create the checkpoint with --file-locks option Additional info: other rpms in my env: runc-1.1.0-2.el9.x86_64 crun-1.4.2-1.el9.x86_64 podman-4.0.0-0.31.el9.x86_64
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.