Fix failure to start api/controller pods with tini as an entrypoint #540
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.
ENTRYPOINT
in a Dockerfile maps tocommand
in a k8s Pod specification, andCMD
in a Dockerfile maps toargs
in a k8s Pod specification. By definingargs
instead ofcommand
, we override the image'sCMD
but not itsENTRYPOINT
and like that we end up successfully usingtini
as an entrypoint.This change relates to this Dockerfile, that has a
ENTRYPOINT
akacommand
set to usetini
.dask-gateway/dask-gateway-server/Dockerfile
Lines 44 to 45 in fd2ada0