This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Only inject/append Entrypoint if it's not already there #2447
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.
Currently the
waypoint-entrypoint
binary is injected into the container and appended to the front of itsEntrypoint
definition (as long asdisable_entrypoint
isfalse
).In the case of using
docker-pull
in thebuild
phase, if the image we pull already has the entrypoint included, this will result in a chain of entrypoints as well as additional layers in the image (see #2381).In this PR, if a container already includes an entry for
/waypoint-entrypoint
in itsEntrypoint
definition, then don't inject it again. We assume that if it is already included in theEntrypoint
definition, that the binary also exists in the container.Fixes #2381