Skip to content

Commit

Permalink
Merge pull request #4375 from GoogleContainerTools/briandealwis-patch-1
Browse files Browse the repository at this point in the history
`debug` now supports buildpacks-produced images
  • Loading branch information
briandealwis authored Jun 23, 2020
2 parents 93169dd + e03e4d8 commit 9d2bab8
Showing 1 changed file with 4 additions and 8 deletions.
12 changes: 4 additions & 8 deletions docs/content/en/docs/pipeline-stages/builders/buildpacks.md
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`.

0 comments on commit 9d2bab8

Please sign in to comment.