Specification for Cloud Native Buildpacks
This specification defines interactions between a platform, a lifecycle, a number of buildpacks, and an application 1. For the purpose of transforming that application into an OCI image and 2. For the purpose of developing or executing automated tests on that application.
A buildpack is software that partially or completely transforms application source code into runnable artifacts.
A lifecycle is software that orchestrates buildpacks and transforms the resulting artifacts into an OCI image.
A platform is software that orchestrates a lifecycle to make buildpack functionality available to end-users such as application developers.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119.
The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the rationale for the C99 standard.
An implementation is not compliant if it fails to satisfy one or more of the MUST, MUST NOT, REQUIRED, SHALL, or SHALL NOT requirements for the protocols it implements. An implementation is compliant if it satisfies all the MUST, MUST NOT, REQUIRED, SHALL, and SHALL NOT requirements for the protocols it implements.
When a word or bullet point is prefixed with a †, it SHALL be assumed to apply only to Linux stacks.
When a word or bullet point is prefixed with a ‡, it SHALL be assumed to apply only to Windows stacks.
When the specification denotes a "shell", Linux stacks MUST use the Bourne Again Shell (
bash) version 3 or greater and Windows stacks MUST use Command Prompt (
cmd.exe) unless otherwise specified.
When the specification denotes a filesystem path using POSIX path notation (e.g.
/cnb/lifecycle), this notation SHALL be interpreted to represent a path where all POSIX file path separators are replaced with the Windows filepath separator (
\) and absolute paths are assumed to be rooted in the default drive (e.g.
When the specification refers to an executable file with POSIX path notation (e.g.
/cnb/buildpacks/bp-a/1.2.3/bin/detect), this notation SHALL be interpreted to represent one of two possible files: one with the suffix
C:\cnb\buildpacks\bp-a\1.2.3\bin\detect.exe) or with the suffix
When the specification refers to a path in the context of an OCI layer tar (e.g.
/cnb/buildpacks/bp-a/1.2.3/), this path SHALL be interpreted to be prefixed with
Files/cnb/buildpacks/bp-a/1.2.3/). Note: path separators in OCI layer tar headers MUST be
/regardless of operating system.
These documents currently specify: