Checkpointing runC container is giving error: Unable to connect a transport socket: Permission denied #2392
Comments
dump.log(00.000118) Version: 3.19 (gitid 0) |
|
That is an unusual error. Can you try it with apparmor disabled? To see if that is related. |
|
Checked with apparmor stopped and disabled, but getting the same error with both the commands |
|
config.json for the container |
I think a traced process has been killed by a fatal signal. You need to find out why it has been killed. Another option is to provide steps how we can reproduce the issue. |
|
A friendly reminder that this issue had no activity for 30 days. |
I'm trying to checkpoint a mysql runC container, the container is in running state with some data already inside and can be accessed from the host as well. Performing a checkpoint using either criu directly or using runc checkpoint is giving me error
Performing a checkpoint using either criu directly or using runc checkpoint is giving me the following error:
Steps to reproduce the issue:
sudo runc checkpoint mysqlorsudo criu dump -t 7227 -vvv -o dump.log && echo OKDescribe the results you received:
Dump fails
Describe the results you expected:
Dump should be successful
Additional information you deem important (e.g. issue happens only occasionally):
I tried with both runc checkpoint and criu dump, both are giving same error. I tried with multiple additional options as well to allow external socket checkpoint, tcp, etc, but nothing worked
CRIU logs and information:
Attached
Output of `criu --version`:
Output of `criu check --all`:
Additional environment details:
Linux Ubuntu 23.04
The text was updated successfully, but these errors were encountered: