💥 api: skip entrypoints by default in withExec
#7136
+90
−86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning
It's a breaking change for anyone currently depending on the entrypoint in
withExec
.To avoid it, users can set
skipEntrypoint: false
today, which will preserve that same behavior after this change.1Alternative solution to:
Container.From
should ignore image entrypoint by default #6574Flipped the default on
withExec
instead. Currently you need to explicitly skip the entrypoint, but with this change, you'll have to explicitly use it instead. Otherwise the entrypoint is still in theContainer
object, and preserved onpublish
.Footnotes
Albeit deprecated until a few releases down the line, so users should be encouraged to change to
useEntrypoint: true
when able. ↩