16 lines
1.2 KiB
Markdown
16 lines
1.2 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 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. If a component has an image for the specified architecture, the playbook will use it directly. If not, it will build the image on the server itself.
|
||
|
|
|
||
|
|
Note that **not all components support self-building yet**.
|
||
|
|
|
||
|
|
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 `*_self_build` variables provided by individual roles.
|