From 765987d423559549577e001d4e3f5355143a25e0 Mon Sep 17 00:00:00 2001 From: mayel Date: Fri, 6 Jan 2023 19:12:50 +0000 Subject: [PATCH] Update 'docs/operators/handbook.md' --- docs/operators/handbook.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md index d5d3756..37346e6 100644 --- a/docs/operators/handbook.md +++ b/docs/operators/handbook.md @@ -312,6 +312,10 @@ Running `server add` with `-d/--debug` should help you debug what is going on un If you need to run a command within a running container you can use `abra app run `. For example, you could run `abra app run cloud.lumbung.space app bash` to open a new bash terminal session inside your remote container. +## How do I attach on a non-running container? + +If you need to run a command on a container that won't start (eg. the container is stuck in a restart loop) you can temporarily disable its default entrypoint by setting it in `compose.yml` to something like ['tail', '-f', '/dev/null'], then redeploy the stack (with `--force --chaos` so you don't need to commit), then [get into the now running container](#how-do-i-attach-to-a-running-container), do your business, and when done revert the compose.yml change and redeploy again. + ## Can I run Co-op Cloud on ARM? `@Mayel`: -- 2.47.2