-
Notifications
You must be signed in to change notification settings - Fork 615
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
Cant make Criu dump work on a GCP node #1230
Comments
Which process are you trying to dump? I have never seen this error before myself or a report of it. We would need a full log file of the dump. Can you run it with |
|
It seems you are trying to checkpoint a process out of a container. This will not work easily. If you resolve the mount problem, you will hit many other problems. What is your goal? Understanding you goal might help to find another solution for your problem. Why aren't you checkpointing the whole container? |
what do u mean? I am getting the pid of the container itself and trying to dump it
|
You cannot (easily) checkpoint a process out of a container without telling CRIU all the details about the resources which are only available in the container. Your first problem is a mount point which is just visible in the container and which CRIU cannot find outside of the container. No one has tried to checkpoint a process out of a running container for a long time as far as I know. |
I am trying to checkpoint the whole container actually I tried to use docker with similar errors
|
Yes, Ubuntu is broken: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257 Use another distribution or another Docker graphdriver. Also see: #860 |
Hi I tried different linux flavors on GCP, and cant make CRIU work
For example if i try an ubuntu machine:
bootstrap code:
then I get the mount error
I also tried to install another version of criu 3.13, same error.
If I try a debian machine, I get similar problem.
Is there a problem with my bootstrap script?
How can i make it work?
The text was updated successfully, but these errors were encountered: