From 0a797110ee14c3188242e97ae3d6a26a41643b12 Mon Sep 17 00:00:00 2001 From: Arve Knudsen Date: Thu, 26 Dec 2024 09:41:19 +0100 Subject: [PATCH] Runbooks: Clarify that container being used to copy files must still be running Signed-off-by: Arve Knudsen --- docs/sources/mimir/manage/mimir-runbooks/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/sources/mimir/manage/mimir-runbooks/_index.md b/docs/sources/mimir/manage/mimir-runbooks/_index.md index ef4bb7884e5..e7a3ed041ef 100644 --- a/docs/sources/mimir/manage/mimir-runbooks/_index.md +++ b/docs/sources/mimir/manage/mimir-runbooks/_index.md @@ -2876,6 +2876,8 @@ For example, you can create a tar of the path you are interested in, and then ex kubectl --namespace mimir exec compactor-0 -c mimir-debug-container -- tar cf - "/proc/1/root/etc/cortex" | tar xf - ``` +Note that the container that you're copying files from must still be running. If you have already exited your debugging container before, that container has stopped, and it cannot be used to copy files. In that case you need to start a new container. + ## Cleanup and Limitations One downside of using [ephemeral containers](https://kubernetes.io/docs/concepts/workloads/pods/ephemeral-containers/#understanding-ephemeral-containers)