Buildpacks

note

This customization interacts with the customization of staging scripts.

note

This page covers the buildpack build mode, which is the default. Applications built from a Dockerfile do not use a builder image at all, see Dockerfile builds.

Trigger-time overrides

You can override staging workload configuration (resources, nodeSelector, tolerations, affinity, TTL, storage, and more) at build trigger-time via the staging API, without changing ConfigMap defaults. See Staging configuration override at trigger time.

By default, Epinio's staging process uses the jammy full stack paketo builder image for Paketo Cloud Native Buildpacks. This converts application sources into deployable application images.

To use a different builder image set the chart keys

• image.builder.repository
• image.builder.tag
• image.builder.userid
• image.builder.groupid

to the desired values before installation.

To override the builder image on an individual basis use the option --builder-image of the epinio push command.

Note also the related documentation about the supported applications.

See also

• Build modes
• Dockerfile builds
• Staging scripts