31 lines
1.7 KiB
Markdown
31 lines
1.7 KiB
Markdown
# Self-building
|
|
|
|
**Caution: self-building does not have to be used on its own. See the [Alternative Architectures](alternative-architectures.md) page.**
|
|
|
|
The playbook supports the self-building of various components, which don't have a container image for your architecture. For `amd64`, self-building is not required.
|
|
|
|
For other architectures (e.g. `arm32`, `arm64`), ready-made container images are used when available. If there's no ready-made image for a specific component and said component supports self-building, an image will be built on the host. Building images like this takes more time and resources (some build tools need to get installed by the playbook to assist building).
|
|
|
|
To make use of self-building, you don't need to do anything besides change your architecture variable (e.g. `matrix_architecture: arm64`). If a component has an image for the specified architecture, the playbook will use it. If not, it will build the image.
|
|
|
|
Note that **not all components support self-building yet**.
|
|
List of roles where self-building the Docker image is currently possible:
|
|
- `matrix-synapse`
|
|
- `matrix-synapse-admin`
|
|
- `matrix-client-element`
|
|
- `matrix-registration`
|
|
- `matrix-coturn`
|
|
- `matrix-corporal`
|
|
- `matrix-ma1sd`
|
|
- `matrix-mailer`
|
|
- `matrix-bridge-appservice-irc`
|
|
- `matrix-bridge-appservice-slack`
|
|
- `matrix-bridge-mautrix-facebook`
|
|
- `matrix-bridge-mautrix-hangouts`
|
|
- `matrix-bridge-mautrix-telegram`
|
|
- `matrix-bridge-mx-puppet-skype`
|
|
|
|
Adding self-building support to other roles is welcome. Feel free to contribute!
|
|
|
|
If you'd like **to force self-building** even if an image is available for your architecture, look into the `matrix_*_self_build` variables provided by individual roles.
|