Skip to content

debug now supports buildpacks-produced images #4375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 23, 2020
Merged

debug now supports buildpacks-produced images #4375

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fe97471
`debug` now supports buildpacks-produced images
briandealwis Jun 23, 2020
e03e4d8
make note an alert
briandealwis Jun 23, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions docs/content/en/docs/pipeline-stages/builders/buildpacks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ To use Buildpacks, add a `buildpack` field to each artifact you specify in the
`artifacts` part of the `build` section. `context` should be a path to
your source.

{{<alert title="Note">}}
In Skaffold 1.11 (schema `v2beta5`), the singular `buildpack` field was renamed to `buildpacks`.
{{</alert>}}

The following options can optionally be configured:

{{< schema root="BuildpackArtifact" >}}
Expand Down Expand Up @@ -70,11 +74,3 @@ buildpacks:
ignore:
- vendor/**
```

### Limitations

The container images produced by Cloud Native Buildpacks [cannot
be configured by `skaffold debug` for debugging]({{< relref "/docs/workflows/debug#unsupported-container-entrypoints" >}}).
These images use a `launcher` binary as an entrypoint to run commands
that are specified in a set of configuration files, which cannot
be altered by `debug`.