New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
returned non-zero after checkpointed #1348
Comments
@qiancai Can you specify what version of criu are you using? |
criu-2.3-2.el7.x86_64 |
Can you give more details about enviroment? What is a kernel version? |
I upgraded the system including criu-2.12-1.el7, and it all work fine now. |
I am sorry but I can still reproduce this. The system is the latest RHEL7.3. |
"runc checkpoint root" returns 0, but than "runc run root" exits with non-zero code. Is it right? Could you reproduce the problem, but run runc with --debug --log /tmp/runc.log options and show the /tmp/runc.log file? |
Still reproducible on criu-3.9 and kernel-4.14. terminal 1> runc --debug --log /tmp/runc.log run root
|
137 means that a container init process was killed by SIGKILL. |
It is a normal behavior for a case when a container is checkpointed. |
process args = "sleep", "6000" in config.json
terminal 1> runc run root
terminal 2> runc checkpoint root
terminal 1> echo $?
terminal 1> 137
The text was updated successfully, but these errors were encountered: