Generate app image from source code
Pack Build uses Cloud Native Buildpacks to create a runnable app image from source code.
Pack Build requires an image name, which will be generated from the source code. Build defaults to the current directory, but you can use --path to specify another source code directory. Build requires a builder, which can either be provided directly to build using --builder, or can be set using the set-default-builder command. For more on how to use pack build, see: https://buildpacks.io/docs/app-developer-guide/build-an-app/.
pack build <image-name> [flags]
pack build test_img --path apps/test-app --builder cnbs/sample-builder:bionic
-B, --builder string Builder image (default "cnbs/sample-builder:bionic")
-b, --buildpack strings Buildpack to use. One of:
a buildpack by id and version in the form of '<buildpack>@<version>',
path to a buildpack directory (not supported on Windows),
path/URL to a buildpack .tar or .tgz file, or
a packaged buildpack image name in the form of '<hostname>/<repo>[:<tag>]'
Repeat for each buildpack in order,
or supply once by comma-separated list
--clear-cache Clear image's associated cache before building
-D, --default-process string Set the default process type. (default "web")
-d, --descriptor string Path to the project descriptor file
-e, --env stringArray Build-time environment variable, in the form 'VAR=VALUE' or 'VAR'.
When using latter value-less form, value will be taken from current
environment at the time this command is executed.
This flag may be specified multiple times and will override
individual values defined by --env-file.
--env-file stringArray Build-time environment variables file
One variable per line, of the form 'VAR=VALUE' or 'VAR'
When using latter value-less form, value will be taken from current
environment at the time this command is executed
-h, --help Help for 'build'
--network string Connect detect and build containers to network
-p, --path string Path to app dir or zip-formatted file (defaults to current working directory)
--publish Publish to registry
--pull-policy string Pull policy to use. Accepted values are always, never, and if-not-present. (default "always")
--run-image string Run image (defaults to default stack's run image)
--trust-builder Trust the provided builder
All lifecycle phases will be run in a single container (if supported by the lifecycle).
--volume stringArray Mount host volume into the build container, in the form '<host path>:<target path>[:<mode>]'.
Repeat for each volume in order,
or supply once by comma-separated list
--no-color Disable color output
-q, --quiet Show less output
--timestamps Enable timestamps in output
-v, --verbose Show more output