Merge branch 'main' into renovate/main-squidfunk-mkdocs-material-8.x
This commit is contained in:
commit
7b84f2da98
|
|
@ -13,7 +13,7 @@ title: Get in touch
|
|||
Here is a link to the [Matrix space](https://matrix.to/#/!xSMwGbdVehScXcIFwS:autonomic.zone?via=autonomic.zone&via=matrix.org&via=1312.media) to see all channels.
|
||||
|
||||
- [`#coopcloud:autonomic.zone`](https://matrix.to/#/!JSVYWCRXSVMrAzgeKB:autonomic.zone?via=autonomic.zone) General chat and announcements (low traffic)
|
||||
- [`#coopcloud-tech:autonomic.zone`](https://matrix.to/#/!IFazIpLtxiScqbHqoa:autonomic.zone?via=autonomic.zone) Technical discussions (some techno babble)
|
||||
- [`#coopcloud-tech:autonomic.zone`](https://matrix.to/#/!DfXPgKLoYCvjHithgS:autonomic.zone?via=autonomic.zone) Technical discussions (some techno babble)
|
||||
- [`#coopcloud-dev:autonomic.zone`](https://matrix.to/#/!IFazIpLtxiScqbHqoa:autonomic.zone?via=autonomic.zone) Intense developer chat (a lot of techno babble)
|
||||
|
||||
### XMPP
|
||||
|
|
|
|||
|
|
@ -249,3 +249,5 @@ Yes! Horizontal scaling is one of the ways Co-op Cloud can really shine. `abra`
|
|||
## Why only x86 support?
|
||||
|
||||
We would love to do ARM support and hope to get there! We've been testing this and [ran into some issues](https://git.autonomic.zone/coop-cloud/organising/issues/25). The TLDR; is that a lot of upstream libre app developer communities are not publishing container builds that support ARM. If they are, there are typically subtle differences in the conventions used to build the image as they are mostly done by community members and not directly taken on by the upstream project themselves. Since one of the core goals is to coordinate and reuse upstream packaging work, we see that ARM support requires a lot of organising and community engagement. Perhaps projects themselves will not want to take on this burden? It is not the role of the Co-op Cloud to set up an entire ARM publishing work flow at this moment in time. We see the benefits of supporting ARM and if you've got ideas / thoughts / approaches for how to make progress here, [please get in touch](/intro/contact/).
|
||||
|
||||
Update: [Can I run Co-op Cloud on ARM?](/operators/handbook/#can-i-run-co-op-cloud-on-arm)
|
||||
|
|
|
|||
|
|
@ -310,4 +310,17 @@ 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 <domain> <service> <command>`. For example, you could run `abra app run cloud.lumbung.space app bash` to open a new bash terminal session inside your remote container.
|
||||
If you need to run a command within a running container you can use `abra app run <domain> <service> <command>`. 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 on ARM?
|
||||
|
||||
`@Mayel`:
|
||||
|
||||
> FYI I've been running on ARM for a while with no troubles (as long as images
|
||||
> used support it of course, `abra` doesn't work yet!) 😀 ... 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
|
||||
|
||||
See [`#312`](https://git.coopcloud.tech/coop-cloud/organising/issues/312) for more.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
mkdocs-awesome-pages-plugin==2.7.0
|
||||
mkdocs-material-extensions==1.0.3
|
||||
mkdocs-material==8.2.8
|
||||
mkdocs-material==8.2.9
|
||||
mkdocs==1.3.0
|
||||
|
|
|
|||
Loading…
Reference in New Issue