This is the third beta release of the Cloud Native Buildpack Lifecycle. This implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.
The lifecycle runs as a normal user in a series of unprivileged Linux containers. To export images and cache image layers, it requires access to a Docker daemon or Docker registry.
.tgz file and copy the lifecycle binaries into a build stack base image. The build image can then be orchestrated by a platform implementation such as the pack CLI or knative.
- Add support for exporting an image to multiple repositories or tags on the same registry (#140).
- Analyzer now permits skipping launch layer metadata restoration with
- Avoid race conditions when previous image changes during the build (#20).