Paketo Buildpacks turn application source code into container images through the Cloud Native Buildpacks specification, reducing containerization work across polyglot teams. section 3.2.3
A builder image orchestrates a sequence of buildpacks, covering concerns such as the operating system, CA certificates, language runtime, and SBOM generation. Builders are OCI images stored in registries and can be customized by platform teams. section 3.2.3
The workflow separates developer and platform responsibilities:
- Developers build applications with a suitable Paketo builder without managing compliance details. section 3.2.3
- Platform teams select community builders or create custom builders for organizational requirements. section 3.2.3
- Organizations can apply the same approach across Java, Go, Node.js, Python, Ruby, Rust, PHP, and other stacks. section 3.2.3
Building a Java application image
A Java application can be packaged with a Paketo builder using pack build or Gradle's bootBuildImage integration, then its image SBOM can be downloaded for inspection. section 3.2.3
Figure 3.6 The Source-to-Image pattern implemented with Cloud Native Buildpacks.
Use the source-to-image diagram to trace how application source passes through Cloud Native Buildpacks into a container image. section 3.2.3
