pack v0.27.0
This is a beta release of the Cloud Native Buildpack local CLI. This platform implementation should be relatively stable and reliable, but breaking changes in the underlying specification may be implemented without notice.
Prerequisites
Install
For instructions on installing pack
, see our installation docs.
Run
Run the command pack
.
You should see the following output
CLI for building apps using Cloud Native Buildpacks
Usage:
pack [command]
Available Commands:
build Generate app image from source code
builder Interact with builders
buildpack Interact with buildpacks
config Interact with your local pack config file
inspect Show information about a built app image
stack Interact with stacks
rebase Rebase app image with latest run image
sbom Interact with SBoM
completion Outputs completion script location
report Display useful information for reporting an issue
version Show current 'pack' version
help Help about any command
Flags:
-h, --help Help for 'pack'
--no-color Disable color output
-q, --quiet Show less output
--timestamps Enable timestamps in output
-v, --verbose Show more output
--version Show current 'pack' version
Use "pack [command] --help" for more information about a command.
Info
Builders created with this release of the pack CLI contain lifecycle v0.14.1 by default.
Changelog
Features
- Update error when bp order group is malformed for meta-buildpacks (#1437 by @imnitishng)
- When pack is run with --verbose, it should not print registry creds (#1433 by @natalieparellano)
- When platform api >= 0.9, analyzer accepts -skip-layers and -launch-cache (#1417 by @natalieparellano)
Known Issues
- Running
pack build
with a builder using lifecycle 0.14.0 yields an error "ERROR: failed to create launch cache".- Cause: buildpacks/lifecycle#847
- Resolutions:
- Option 1: Use a builder with
lifecycle
>= 0.14.1.
pack builder inspect <builder-image>
can be used to inspect a builder image. - Option 2: Use
--lifecycle-image=buildpacksio/lifecycle:0.14.1 --trust-builder=false
flags withpack build
.
These flags would make pack use the patched version of the lifecycle for theanalyze
,restore
andexport
phases.
Learn more.
- Option 1: Use a builder with
Contributors
We'd like to acknowledge that this release wouldn't be as good without the help of the following amazing contributors:
@dependabot[bot], @dfreilich, @imnitishng, @jromero, @natalieparellano