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

<!--
SPDX-FileCopyrightText: 2024 MDAD Team and contributors

SPDX-License-Identifier: AGPL-3.0-or-later
-->

# Alternative architectures

As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported.

The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:

- `amd64` (`x86_64`)
- `arm32`
- `arm64`

Some tools and container images can be built on the host or other measures can be used to install on that architecture.

## Implementation details

For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building).

For other architecture (`arm64`, `arm32`), 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.
Setting up REUSE: add copyright statements to files in docs/ Note that files in docs/assets/ are managed with REUSE.toml Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org> 2024-12-07 10:46:15 +01:00			`<!--`
			`SPDX-FileCopyrightText: 2024 MDAD Team and contributors`

			`SPDX-License-Identifier: AGPL-3.0-or-later`
			`-->`

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 2020-04-18 22:55:19 +02:00			`# Alternative architectures`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 2020-06-09 06:54:42 +02:00
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			As stated in the [Prerequisites](prerequisites.md), currently only `amd64` (`x86_64`) is fully supported.
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 2020-04-18 22:55:19 +02:00
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			The playbook automatically determines the target server's architecture (the `matrix_architecture` variable) to be one of the following:
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 2020-06-09 06:54:42 +02:00
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			- `amd64` (`x86_64`)
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 2020-04-18 22:55:19 +02:00			- `arm32`
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			- `arm64`
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 2020-04-18 22:55:19 +02:00
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			`Some tools and container images can be built on the host or other measures can be used to install on that architecture.`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 2020-06-09 06:54:42 +02:00
clarification for the list of implementation details 2020-04-19 13:32:27 +02:00			`## Implementation details`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 2020-06-09 06:54:42 +02:00
Mention that Hydrogen always undergoes self-building 2021-10-27 13:00:40 +02:00			For `amd64`, prebuilt container images (see the [container images we use](container-images.md)) are used for all components (except [Hydrogen](configuring-playbook-client-hydrogen.md), which goes through self-building).
clarification for the list of implementation details 2020-04-19 13:32:27 +02:00
Determine matrix_architecture automatically 2022-11-22 08:09:11 +01:00			For other architecture (`arm64`, `arm32`), 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.