container/entrypoint¶
Entrypoint override for a container created by the generic containerStart action.
The entrypoint the created container runs, e.g. /bin/sh.
Omitting this parameter and passing it as an empty string mean different things.
- Omitted entirely,
containerStartuses/usr/bin/drpcli, matching the machine-bound runner path's behavior of overriding the image's own ENTRYPOINT to run a DRP runner. This is the default because the runner images this plugin was built for expect it. - Passed as the empty string (
""), the image's own ENTRYPOINT is left alone: no--entrypointflag is emitted at all. This is what you want for any image that is not a DRP runner image, because/usr/bin/drpclidoes not exist inside it and the container would fail to start with no PID 1. - Any other value is used as given.
So containerStart with container/image: alpine needs
container/entrypoint: "" (or an entrypoint that exists in the image),
together with a container/command for the container to run.
This parameter deliberately declares no schema default, and one must
not be added. DRP substitutes a param's schema default for any absent
optional action parameter before the plugin ever sees the invocation, so
a default: here would make the parameter arrive as present-and-empty on
every call. "Omitted" would become unreachable, and every caller --
including the machine-shaped ones that need /usr/bin/drpcli -- would
silently get the image's own ENTRYPOINT instead. The absence of a default
is load-bearing, not an oversight.
Objects that Reference container/entrypoint¶
Not used in current content packs
Objects used by container/entrypoint¶
Not used in current content packs