matrix-docker-ansible-deploy/docs/alternative-architectures.md

# Alternative architectures

As stated in the [Prerequisites](prerequisites.md), currently only `x86_64` is fully supported. However, it is possible to set the target architecture, and some tools can be built on the host or other measures can be used.

To that end add the following variable to your `vars.yaml` file:

```yaml
matrix_architecture: <your-matrix-server-architecture>
```

Currently supported architectures are the following:
- `amd64` (the default)
- `arm64`
- `arm32`

so for the Raspberry Pi, the following should be in your `vars.yaml` file:

```yaml
matrix_architecture: "arm32"
```

## Implementation details

For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used everywhere, because all images are available for this architecture.

For other architectures, components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary.
add experimental(?) architecture support for arm32 and arm64 the changes are necessary because certbot images are tagged, so docker does not recognize the necessary architecture 4 years ago			`# Alternative architectures`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 4 years ago
Update docs on self-building and remove useless variable `matrix_container_images_self_build` was not really doing anything anymore. It previously was influencing `matrix__self_build` variables, but it's no longer the case since some time ago. Individual `matrix__self_build` variables are still available. People that would like to toggle self-building for a specific component ought to use those. These variables are also controlled automatically (via `group_vars/matrix_servers`) depending on `matrix_architecture`. In other words, self-building is being done automatically for all components when they don't have a prebuilt image for the specified architecture. Some components only support `amd64`, while others also have images for other architectures. 4 years ago			As stated in the [Prerequisites](prerequisites.md), currently only `x86_64` is fully supported. However, it is possible to set the target architecture, and some tools can be built on the host or other measures can be used.
add experimental(?) architecture support for arm32 and arm64 the changes are necessary because certbot images are tagged, so docker does not recognize the necessary architecture 4 years ago
			To that end add the following variable to your `vars.yaml` file:
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 4 years ago
			```yaml
Fix typos 4 years ago			`matrix_architecture: <your-matrix-server-architecture>`
add experimental(?) architecture support for arm32 and arm64 the changes are necessary because certbot images are tagged, so docker does not recognize the necessary architecture 4 years ago			```
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 4 years ago
add experimental(?) architecture support for arm32 and arm64 the changes are necessary because certbot images are tagged, so docker does not recognize the necessary architecture 4 years ago			`Currently supported architectures are the following:`
			- `amd64` (the default)
			- `arm64`
			- `arm32`

Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 4 years ago			so for the Raspberry Pi, the following should be in your `vars.yaml` file:

			```yaml
Fix typos 4 years ago			`matrix_architecture: "arm32"`
add explicit information for the Rapsberry pi 4 years ago			```

clarification for the list of implementation details 4 years ago			`## Implementation details`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 4 years ago
Fix wording a bit 3 years ago			For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used everywhere, because all images are available for this architecture.
clarification for the list of implementation details 4 years ago
Update docs on self-building and remove useless variable `matrix_container_images_self_build` was not really doing anything anymore. It previously was influencing `matrix__self_build` variables, but it's no longer the case since some time ago. Individual `matrix__self_build` variables are still available. People that would like to toggle self-building for a specific component ought to use those. These variables are also controlled automatically (via `group_vars/matrix_servers`) depending on `matrix_architecture`. In other words, self-building is being done automatically for all components when they don't have a prebuilt image for the specified architecture. Some components only support `amd64`, while others also have images for other architectures. 4 years ago			`For other architectures, components which have a prebuilt image make use of it. If the component is not available for the specific architecture, [self-building](self-building.md) will be used. Not all components support self-building though, so your mileage may vary.`