From 39d89e4a93ce1a53fd0c6764efda3134f17bef98 Mon Sep 17 00:00:00 2001 From: Kevin Krakauer Date: Thu, 27 Jul 2023 11:19:50 -0700 Subject: [PATCH] site: note that flags passed to run should be replicated for restore PiperOrigin-RevId: 551588446 --- g3doc/user_guide/checkpoint_restore.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/g3doc/user_guide/checkpoint_restore.md b/g3doc/user_guide/checkpoint_restore.md index 0ab0911b0..5d685bdb9 100644 --- a/g3doc/user_guide/checkpoint_restore.md +++ b/g3doc/user_guide/checkpoint_restore.md @@ -31,9 +31,9 @@ continue to run after the checkpoint has been made. (By default, containers stop their processes after committing a checkpoint.) > Note: All top-level runsc flags needed when calling run must be provided to -> checkpoint if --leave-running is used. +> checkpoint if `--leave-running` is used. -> Note: --leave-running functions by causing an immediate restore so the +> Note: `--leave-running` functions by causing an immediate restore so the > container, although will maintain its given container id, may have a different > process id. @@ -51,6 +51,9 @@ runsc create runsc restore --image-path= ``` +> Note: All top-level runsc flags needed when calling run must be provided to +> `restore`. + ## How to use checkpoint/restore in Docker: Currently checkpoint/restore through `runsc` is not entirely compatible with