Managing the Store

Page last updated:

The Store provides a collection of buildpacks that can be utilized by Builders. Buildpacks are distributed and added to the store in buildpackages which are docker images.

Build Service ships with curated collection of Tanzu buildpacks for Java, Nodejs, Python, go, PHP, httpd, and Dotnet. It is important to keep these buildpacks up-to-date. Updates to these buildpacks are provided on the Tanzu Network Build Service Dependency page.

In addition to supported Tanzu buildpacks, custom buildpackages can be uploaded to the Build Service store.

Note: Only Build Service Admins can perform store commands.

Adding Buildpackages to the Store

Users can add multiple buildpackages at a time from a Docker registry or from a file on the local machine:

  • If using a Docker registry:

    pb store add <buildpackage-1> <buildpackage-2> ...
    

Note: The user must have read access to the source Docker registry and write access to build service registry on the local machine.

  • If using local stack images created with docker save:

    pb store add <path-to-buildpackage-1>.tar <path-to-buildpackage-2>.tar ...  --local
    

Note: At this time pb does not support the .cnb buildpackage format

Creating Buildpackages

Documentation for creating buildpackages is available here.

A buildpackage can be packaged into a build service ready buildpackage with:

pack package-buildpack

Removing Buildpackages from the Store

Users can remove a buildpackage from the store:

pb store remove <buildpackage>

Listing Buildpackages in the Store

To list the buildpackages & buildpacks in the store:

pb store list

To list buildpackages & buildpacks and the display the order of “meta-buildpacks”:

pb store list --order

Note: The output of this command is helpful because it mirrors the format used when creating custom builders.

Corresponding kpack Resource

All Build Service builders utilize a cluster scoped Store Resource with the name build-service-store.