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

# 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.
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 5 years ago			`# Alternative architectures`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 5 years ago
Determine matrix_architecture automatically 2 years ago			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 5 years ago
Determine matrix_architecture automatically 2 years ago			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). 5 years ago
Determine matrix_architecture automatically 2 years ago			- `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 5 years ago			- `arm32`
Determine matrix_architecture automatically 2 years ago			- `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 5 years ago
Determine matrix_architecture automatically 2 years ago			`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). 5 years ago
add explicit information for the Rapsberry pi 5 years ago
clarification for the list of implementation details 5 years ago			`## Implementation details`
Fix certbot/cerbot image pulling for ARM32 and ARM64 Related to #529 (Github Issue). 5 years ago
Mention that Hydrogen always undergoes self-building 3 years ago			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 5 years ago
Determine matrix_architecture automatically 2 years ago			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.