From 26561b758bec575571cf2dda5a2a7c9e2c592ca8 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Sun, 17 Apr 2022 23:52:41 +0200 Subject: [PATCH] ARM is doable --- docs/operators/handbook.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md index 22b9090..e8afe5e 100644 --- a/docs/operators/handbook.md +++ b/docs/operators/handbook.md @@ -310,4 +310,15 @@ Running `server add` with `-d/--debug` should help you debug what is going on un ## How do I attach to a running container? -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. \ No newline at end of file +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. + +## Can I run Co-op Cloud or ARM? + +`@Mayel`: + +> FYI I've been running on ARM (both the servers and abra client) for a while +> with no troubles (as long as images used support it of course) 😀 ... in +> cases where I couldn't find a multiarch image I simply have eg. image: +> ${DB_DOCKER_IMAGE} in the docker-compose and set that to a compatible image +> in the env config ... there was really nothing to it, apart from making sure +> to use multiarch or arm images