diff --git a/content/docs/app-developer-guide/run-an-app.md b/content/docs/app-developer-guide/run-an-app.md index 3f2e272b3..08cf61351 100644 --- a/content/docs/app-developer-guide/run-an-app.md +++ b/content/docs/app-developer-guide/run-an-app.md @@ -50,6 +50,8 @@ Base Image: Run Images: cnbs/sample-stack-run:alpine +Rebasable: true + Buildpacks: ID VERSION HOMEPAGE samples/java-maven 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven diff --git a/content/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials.md b/content/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials.md index 027e9502f..c97a18713 100644 --- a/content/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials.md +++ b/content/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials.md @@ -10,6 +10,7 @@ One of the benefits of buildpacks is they can also populate the app image with m * The process types that are available and the commands associated with them * The run-image the app image was based on * The buildpacks were used to create the app image +* Whether the run-image can be rebased with a new version through the `Rebasable` label or not * And more...! You can find some of this information using `pack` via its `inspect-image` command. The bill-of-materials information will be available using `pack sbom download`. diff --git a/katacoda/scenarios/app-developer-guide/run-an-app.md b/katacoda/scenarios/app-developer-guide/run-an-app.md index 2cfe643be..23ef74769 100644 --- a/katacoda/scenarios/app-developer-guide/run-an-app.md +++ b/katacoda/scenarios/app-developer-guide/run-an-app.md @@ -42,6 +42,8 @@ Base Image: Run Images: cnbs/sample-stack-run:alpine +Rebasable: true + Buildpacks: ID VERSION HOMEPAGE samples/java-maven 0.0.1 https://github.com/buildpacks/samples/tree/main/buildpacks/java-maven