Stay organized with collections
Save and categorize content based on your preferences.
Name
kf wrap-v2-buildpack - Create a V3 buildpack that wraps a V2 buildpack.
Synopsis
kf wrap-v2-buildpack NAME V2_BUILDPACK_URL|PATH [flags]
Description
Creates a V3 buildpack that wraps a V2 buildpack.
The resulting buildpack can then be used with other V3 buildpacks by
creating a builder. See
https://buildpacks.io/docs/operator-guide/create-a-builder/ for more
information.
A V3 buildpack is packaged as an OCI container. If the --publish flag
is provided, then the container will be published to the corresponding
container repository.
This command uses other CLIs under the hood. This means the following
CLIs need to be available on the path:
* go
* git
* pack
* cp
* unzip
We recommend using Cloud Shell to ensure these CLIs are available and
the correct version.
Examples
# Download buildpack from the given git URL. Uses the git CLI to
# download the repository.
kf wrap-v2-buildpack gcr.io/some-project/some-name https://github.com/some/buildpack
# Creates the buildpack from the given path.
kf wrap-v2-buildpack gcr.io/some-project/some-name path/to/buildpack
# Creates the buildpack from the given archive file.
kf wrap-v2-buildpack gcr.io/some-project/some-name path/to/buildpack.zip
Flags
--builder-repo=string
Builder repo to use. (default "github.com/poy/buildpackapplifecycle/builder")
--buildpack-stacks=stringArray
Stack(s) this buildpack will be compatible with. (default [google])
--buildpack-version=string
Version of the resulting buildpack. This will be used as the image tag. (default "0.0.1")
-h, --help
help for wrap-v2-buildpack
--launcher-repo=string
Launcher repo to use. (default "github.com/poy/buildpackapplifecycle/launcher")
--output-dir=string
Output directory for the buildpack data (before it's packed). If left empty, a temp dir will be used.
--publish
Publish the buildpack image.
Inherited flags
These flags are inherited from parent commands.
--as=string
Username to impersonate for the operation.
--as-group=strings
Group to impersonate for the operation. Include this flag multiple times to specify multiple groups.
--config=string
Path to the Kf config file to use for CLI requests.
--kubeconfig=string
Path to the kubeconfig file to use for CLI requests.
--log-http
Log HTTP requests to standard error.
--space=string
Space to run the command against. This flag overrides the currently targeted Space.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# kf wrap-v2-buildpack\n\n### Name\n\n`kf wrap-v2-buildpack` - Create a V3 buildpack that wraps a V2 buildpack.\n\n### Synopsis\n\n```\nkf wrap-v2-buildpack NAME V2_BUILDPACK_URL|PATH [flags]\n```\n\n### Description\n\nCreates a V3 buildpack that wraps a V2 buildpack.\n\nThe resulting buildpack can then be used with other V3 buildpacks by\ncreating a builder. See\nhttps://buildpacks.io/docs/operator-guide/create-a-builder/ for more\ninformation.\n\nA V3 buildpack is packaged as an OCI container. If the --publish flag\nis provided, then the container will be published to the corresponding\ncontainer repository.\n\nThis command uses other CLIs under the hood. This means the following\nCLIs need to be available on the path:\n\\* go\n\\* git\n\\* pack\n\\* cp\n\\* unzip\n\nWe recommend using Cloud Shell to ensure these CLIs are available and\nthe correct version.\n\n### Examples\n\n```\n# Download buildpack from the given git URL. Uses the git CLI to\n# download the repository.\nkf wrap-v2-buildpack gcr.io/some-project/some-name https://github.com/some/buildpack\n\n# Creates the buildpack from the given path.\nkf wrap-v2-buildpack gcr.io/some-project/some-name path/to/buildpack\n\n# Creates the buildpack from the given archive file.\nkf wrap-v2-buildpack gcr.io/some-project/some-name path/to/buildpack.zip\n```\n\n### Flags\n\n`--builder-repo=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Builder repo to use. (default \"github.com/poy/buildpackapplifecycle/builder\")\n\n`--buildpack-stacks=`\u003cvar translate=\"no\"\u003estringArray\u003c/var\u003e\n\n: Stack(s) this buildpack will be compatible with. (default \\[google\\])\n\n`--buildpack-version=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Version of the resulting buildpack. This will be used as the image tag. (default \"0.0.1\")\n\n`-h, --help`\n\n: help for wrap-v2-buildpack\n\n`--launcher-repo=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Launcher repo to use. (default \"github.com/poy/buildpackapplifecycle/launcher\")\n\n`--output-dir=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Output directory for the buildpack data (before it's packed). If left empty, a temp dir will be used.\n\n`--publish`\n\n: Publish the buildpack image.\n\n### Inherited flags\n\nThese flags are inherited from parent commands.\n\n`--as=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Username to impersonate for the operation.\n\n`--as-group=`\u003cvar translate=\"no\"\u003estrings\u003c/var\u003e\n\n: Group to impersonate for the operation. Include this flag multiple times to specify multiple groups.\n\n`--config=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Path to the Kf config file to use for CLI requests.\n\n`--kubeconfig=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Path to the kubeconfig file to use for CLI requests.\n\n`--log-http`\n\n: Log HTTP requests to standard error.\n\n`--space=`\u003cvar translate=\"no\"\u003estring\u003c/var\u003e\n\n: Space to run the command against. This flag overrides the currently targeted Space."]]
