Argo: Argo is not respecting container default entry point

Created on 2 Dec 2020  路  2Comments  路  Source: argoproj/argo

Summary

I want argo to choose the default entry point of a container. It does not.

      container:
        image:workflow-step-XXX:e72b5997
        args: ["{{inputs.parameters}}"]

fails and the following works:

      container:
        image:workflow-step-XXX:e72b5997
        args: ["{{inputs.parameters}}"]
        command: ["/check-preconditions"]

When I directly docker run the container the entry point works as expected

Diagnostics

What Kubernetes provider are you using?

GCE

What version of Argo Workflows are you running?

v2.11.1



Message from the maintainers:

Impacted by this bug? Give it a 馃憤. We prioritise the issues with the most 馃憤.

bug

Most helpful comment

Argo workflows only creates PODs, does not touch command or args in the POD spec, if your entrypoint doesn't work which means your k8s is not honoring the entrypoint of your container.

All 2 comments

Argo workflows only creates PODs, does not touch command or args in the POD spec, if your entrypoint doesn't work which means your k8s is not honoring the entrypoint of your container.

Oh. Thanks for that info!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

iterion picture iterion  路  3Comments

vicaire picture vicaire  路  4Comments

basanthjenuhb picture basanthjenuhb  路  3Comments

tigerwings picture tigerwings  路  3Comments

srados picture srados  路  3Comments