You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a script with an args with sh (and not a command). Our image has an entrypoint and exec the rest of the arguments with something like exec "$@".
The PR #4492 breaks these types of workflows (see the example below).
I don't know what should be the right behavior but executing the entrypoint before a script is pretty convenient. For instance, we use it to do some privileged actions and then we drop privileges before executing the workflow's script.
Diagnostics
What Kubernetes provider are you using? Baremetal
What version of Argo Workflows are you running? v2.12.2
Summary
We use a script with an
args
withsh
(and not acommand
). Our image has an entrypoint and exec the rest of the arguments with something likeexec "$@"
.The PR #4492 breaks these types of workflows (see the example below).
I don't know what should be the right behavior but executing the entrypoint before a script is pretty convenient. For instance, we use it to do some privileged actions and then we drop privileges before executing the workflow's script.
Diagnostics
What Kubernetes provider are you using? Baremetal
What version of Argo Workflows are you running? v2.12.2
My test image is built using these files :
Dockerfile :
entrypoint.sh :
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: