pack v0.2.1

pack v0.2.1

This is a patch to the second 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. Note that pack is intended for local image builds, and thus requires a Docker daemon. The lifecycle should be used directly when building on cloud platforms.

Prerequisites

• The Docker daemon must be installed on your workstation or accessible over the network.

Install

If you're on macOS, you can use Homebrew:

$ brew tap buildpack/tap
$ brew install pack

Otherwise:

1. Download the .tgz or .zip file for your platform
2. Extract the pack binary
3. (Optional) Add the directory containing pack to PATH, or copy pack to a directory like /usr/local/bin

Run

Run the command pack.

You should see the following output

Usage:
  pack [command]

Available Commands:
  build                 Generate app image from source code
  run                   Build and run app image (recommended for development only)
  rebase                Rebase app image with latest run image
  create-builder        Create builder image
  set-run-image-mirrors Set mirrors to other repositories for a given run image
  inspect-builder       Show information about a builder
  set-default-builder   Set default builder used by other commands
  suggest-builders      Display list of recommended builders
  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

Use "pack [command] --help" for more information about a command.

Fixes

• Fix critical bug that results in a failure to restore layer metadata to the correct location (buildpacks/lifecycle#137).
• Move detection results to the beginning of each line (buildpacks/lifecycle#134).

NOTE: All changes in this patch are from the corresponding lifecycle release.

Known Issues

• Publishing to a private registry from Windows still fails in some cases (#109). We have fixed this upstream in Docker for Windows (docker/docker-credential-helpers#139), but Docker will need to ship a new version to fix this bug.