diff --git a/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/index.html b/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/index.html index 8931f09e9..a2518d413 100644 --- a/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/index.html +++ b/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/index.html @@ -922,7 +922,7 @@
This command will create node-js-buildpack
directory which contains buildpack.toml
, bin/build
, bin/detect
files.
-a, --api
Buildpack API compatibility of the generated buildpack-h, --help
Help for ’new'--path
the location on the filesystem to generate the artifacts--stacks
Stacks (deprecated) the buildpack will work with-V, --version
the version of the buildpack in buildpack.tomlThe buildpack ID is the way you will reference the buildpack when you create buildpack groups, builders, etc. Targets identifies the kind of build and run base images the buildpack will work with. The stack ID (deprecated) uniquely identifies a build and run image configuration the buildpack will work with. This example can be run on Ubuntu Noble.
@@ -989,9 +985,9 @@pack
===> DETECTING
...
-err: examples/node-js@0.0.1 (1)
-ERROR: No buildpack groups passed detection.
-ERROR: failed to detect: buildpack(s) failed with err
+[detector] err: examples/node-js@0.0.1 (1)
+[detector] ERROR: No buildpack groups passed detection.
+[detector] ERROR: failed to detect: buildpack(s) failed with err
ERROR: failed to build: executing lifecycle: failed with status code: 21
diff --git a/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app/index.html b/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app/index.html
index e9691d115..4e8a6d47b 100644
--- a/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app/index.html
+++ b/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app/index.html
@@ -965,8 +965,8 @@ Running the Build
...
===> RESTORING
===> BUILDING
----> NodeJS Buildpack
----> Downloading and extracting NodeJS
+[builder] ---> NodeJS Buildpack
+[builder] ---> Downloading and extracting NodeJS
...
===> EXPORTING
...
diff --git a/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching/index.html b/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching/index.html
index f1970ef48..c2786a3be 100644
--- a/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching/index.html
+++ b/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching/index.html
@@ -1007,8 +1007,8 @@ Cache the runtime layer
===> BUILDING
...
----> NodeJS Buildpack
------> Reusing NodeJS
+[builder] ---> NodeJS Buildpack
+[builder] -----> Reusing NodeJS
Next, let’s see how buildpack users may be able to provide configuration to the buildpack.
diff --git a/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable/index.html b/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable/index.html
index bbffffcd5..1a40d438b 100644
--- a/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable/index.html
+++ b/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable/index.html
@@ -990,8 +990,8 @@ Select NodeJS version
===> BUILDING
...
----> NodeJS Buildpack
------> Downloading and extracting NodeJS 18.18.1
+[builder] ---> NodeJS Buildpack
+[builder] -----> Downloading and extracting NodeJS 18.18.1
Going further
Now that you’ve finished your buildpack, how about extending it? Try:
diff --git a/docs/for-buildpack-authors/tutorials/basic-buildpack/index.xml b/docs/for-buildpack-authors/tutorials/basic-buildpack/index.xml
index b9e8b85f5..aba2fe787 100644
--- a/docs/for-buildpack-authors/tutorials/basic-buildpack/index.xml
+++ b/docs/for-buildpack-authors/tutorials/basic-buildpack/index.xml
@@ -19,7 +19,7 @@
https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/
Mon, 01 Jan 0001 00:00:00 +0000
https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/
- <!-- test:suite=create-buildpack;weight=2 -->
<p>Now we will set up the buildpack scaffolding.</p>
<p>Let’s create the directory where your buildpack will live:</p>
<h2 id="using-the-pack-cli">Using the Pack CLI</h2>
<p>The <code>buildpack new <id></code> command will create a directory named for the buildpack ID.
Make sure to run this command outside the <code>node-js-sample-app</code> directory created previously.</p>
<p>Example:</p>
<!-- test:exec -->
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">pack buildpack new examples/node-js <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --api 0.10 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --path node-js-buildpack <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --version 0.0.1 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --stacks io.buildpacks.samples.stacks.noble
</span></span></code></pre></div><!--+- "{{execute}}"+-->
<p>This command will create <code>node-js-buildpack</code> directory which contains <code>buildpack.toml</code>, <code>bin/build</code>, <code>bin/detect</code> files.</p>
+ <!-- test:suite=create-buildpack;weight=2 -->
<p>Now we will set up the buildpack scaffolding.</p>
<p>Let’s create the directory where your buildpack will live:</p>
<h2 id="using-the-pack-cli">Using the Pack CLI</h2>
<p>The <code>buildpack new <id></code> command will create a directory named for the buildpack ID.
Make sure to run this command outside the <code>node-js-sample-app</code> directory created previously.</p>
<p>Example:</p>
<!-- test:exec -->
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">pack buildpack new examples/node-js <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --api 0.10 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --path node-js-buildpack <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --version 0.0.1 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --targets <span class="s2">"linux/amd64"</span>
</span></span></code></pre></div><!--+- "{{execute}}"+-->
<p>This command will create <code>node-js-buildpack</code> directory which contains <code>buildpack.toml</code>, <code>bin/build</code>, <code>bin/detect</code> files.</p>
-
Detecting your application
diff --git a/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles/index.html b/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles/index.html
index f59998c91..62bb0707b 100644
--- a/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles/index.html
+++ b/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles/index.html
@@ -929,6 +929,7 @@ Create a builder with e
pack builder create localhost:5000/extensions-builder \
--config $PWD/samples/builders/alpine/builder.toml \
+ --target "linux/amd64" \
--publish
Build the application image
Run pack build
(note that the “source” directory is effectively ignored in our example):
diff --git a/docs/for-platform-operators/how-to/integrate-ci/pack/cli/pack_config_lifecycle-image/index.html b/docs/for-platform-operators/how-to/integrate-ci/pack/cli/pack_config_lifecycle-image/index.html
index b4af19c5e..cdf1d16c9 100644
--- a/docs/for-platform-operators/how-to/integrate-ci/pack/cli/pack_config_lifecycle-image/index.html
+++ b/docs/for-platform-operators/how-to/integrate-ci/pack/cli/pack_config_lifecycle-image/index.html
@@ -906,11 +906,11 @@ pack config lifecycle-image
pack config lifecycle-image
Configure a custom container image for the lifecycle
Synopsis
-You can use this command to set a custom image to fetch the lifecycle from.This will be used for untrusted builders. If unset, defaults to: buildpacksio/lifecycleFor more on trusted builders, and when to trust or untrust a builder, check out our docs here: https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/
+You can use this command to set a custom image to fetch the lifecycle from.This will be used for untrusted builders. If unset, defaults to: docker.io/buildpacksio/lifecycleFor more on trusted builders, and when to trust or untrust a builder, check out our docs here: https://buildpacks.io/docs/tools/pack/concepts/trusted_builders/
pack config lifecycle-image <lifecycle-image> [flags]
Options
-h, --help Help for 'lifecycle-image'
- -u, --unset Unset custom lifecycle image, and use the lifecycle images from [94mbuildpacksio/lifecycle[0m
+ -u, --unset Unset custom lifecycle image, and use the lifecycle images from [94mdocker.io/buildpacksio/lifecycle[0m
Options inherited from parent commands
--force-color Force color output
--no-color Disable color output
diff --git a/docs/for-platform-operators/how-to/integrate-ci/pack/index.html b/docs/for-platform-operators/how-to/integrate-ci/pack/index.html
index 5c2c879b5..fbf0c66ef 100644
--- a/docs/for-platform-operators/how-to/integrate-ci/pack/index.html
+++ b/docs/for-platform-operators/how-to/integrate-ci/pack/index.html
@@ -919,7 +919,7 @@ Pack
pack
CLI
Install
-You can install the most recent version of the pack
CLI (version 0.35.1) on the following operating systems:
+You can install the most recent version of the pack
CLI (version 0.36.0) on the following operating systems:
@@ -1001,7 +1001,7 @@ Tags
- Use a version tag to pin a specific release:
-buildpacksio/pack:0.35.1
+buildpacksio/pack:0.36.0
- other versions
@@ -1040,7 +1040,7 @@ Usage
The following command will download the latest version of pack
from GitHub and install it in /usr/local/bin/
.
-(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-linux.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
+(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-linux.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
@@ -1101,7 +1101,7 @@ Tags
- Use a version tag to pin a specific release:
-buildpacksio/pack:0.35.1
+buildpacksio/pack:0.36.0
- other versions
@@ -1131,9 +1131,9 @@ Usage
The following command will download the latest version of pack
from GitHub and install it in /usr/local/bin/
.
Intel:
-(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-macos.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
+(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-macos.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
Apple Silicon:
-(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.35.1/pack-v0.35.1-macos-arm64.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
+(curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.36.0/pack-v0.36.0-macos-arm64.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)
@@ -1185,7 +1185,7 @@ Usage
To install pack
on Windows, we recommend using Chocolatey:
-choco install pack --version=0.35.1
+choco install pack --version=0.36.0
@@ -1202,7 +1202,7 @@ Tags
- Use a version tag to pin a specific release:
-buildpacksio/pack:0.35.1
+buildpacksio/pack:0.36.0
- other versions
diff --git a/index.html b/index.html
index 9c72a43cb..0ecf4c2be 100644
--- a/index.html
+++ b/index.html
@@ -2,7 +2,7 @@
-
+
diff --git a/index.xml b/index.xml
index 52d632915..27e0a1ab9 100644
--- a/index.xml
+++ b/index.xml
@@ -236,7 +236,7 @@
https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/
Mon, 01 Jan 0001 00:00:00 +0000
https://buildpacks.io/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb/
- <!-- test:suite=create-buildpack;weight=2 -->
<p>Now we will set up the buildpack scaffolding.</p>
<p>Let’s create the directory where your buildpack will live:</p>
<h2 id="using-the-pack-cli">Using the Pack CLI</h2>
<p>The <code>buildpack new <id></code> command will create a directory named for the buildpack ID.
Make sure to run this command outside the <code>node-js-sample-app</code> directory created previously.</p>
<p>Example:</p>
<!-- test:exec -->
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">pack buildpack new examples/node-js <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --api 0.10 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --path node-js-buildpack <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --version 0.0.1 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --stacks io.buildpacks.samples.stacks.noble
</span></span></code></pre></div><!--+- "{{execute}}"+-->
<p>This command will create <code>node-js-buildpack</code> directory which contains <code>buildpack.toml</code>, <code>bin/build</code>, <code>bin/detect</code> files.</p>
+ <!-- test:suite=create-buildpack;weight=2 -->
<p>Now we will set up the buildpack scaffolding.</p>
<p>Let’s create the directory where your buildpack will live:</p>
<h2 id="using-the-pack-cli">Using the Pack CLI</h2>
<p>The <code>buildpack new <id></code> command will create a directory named for the buildpack ID.
Make sure to run this command outside the <code>node-js-sample-app</code> directory created previously.</p>
<p>Example:</p>
<!-- test:exec -->
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">pack buildpack new examples/node-js <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --api 0.10 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --path node-js-buildpack <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --version 0.0.1 <span class="se">\
</span></span></span><span class="line"><span class="cl"><span class="se"></span> --targets <span class="s2">"linux/amd64"</span>
</span></span></code></pre></div><!--+- "{{execute}}"+-->
<p>This command will create <code>node-js-buildpack</code> directory which contains <code>buildpack.toml</code>, <code>bin/build</code>, <code>bin/detect</code> files.</p>
-
Use the build plan