In many scenarios, users need to change the TCP port bound to a socket before restoring a container (e.g., checkpoint-restore/criu#2710). CRIU saves this port in files.img, which is included in the checkpoint tar archive.
Currently, the only way to restore a container with a different port is to manually edit the checkpoint before restore. It would be great if checkpointctl provides such functionality, similar to the --tcp-listen-remap option of criu-image-streamer or the edit_files_img.py script.
In many scenarios, users need to change the TCP port bound to a socket before restoring a container (e.g., checkpoint-restore/criu#2710). CRIU saves this port in
files.img, which is included in the checkpoint tar archive.Currently, the only way to restore a container with a different port is to manually edit the checkpoint before restore. It would be great if
checkpointctlprovides such functionality, similar to the--tcp-listen-remapoption of criu-image-streamer or the edit_files_img.py script.