Clemens
12/09/2020, 3:01 PM0.13.19.
. As environments are being deprecated I am trying to move the flows over to run_config setup.
I am using the Docker storage and KubernetesRun for run_config. I noticed that the container that is built with KubernetesRun()
is configured with:
command: /bin/sh -c
command arguments: prefect execute flow-run
but when I inject a job spec file with`KubernetesRun(job_template_path="job_specs.yaml")` (as I need to to access the Kubernetes secrets that I need for the flow to run) only the command arguments
are written by the prefect build and the command
is left blank. That leads to the container failing with an "executable not found"
A workaround is to specifically include the command
section in the job specs file command: ["/bin/sh", "-c"]
.
That doesn’t seem to be expected behaviour, or am I missing something?josh
12/09/2020, 3:14 PMcommand
and I think that by using a custom job template it is assuming you have the command set. I’m going to open an issue on the repo to verify if that is intended behavior and if it is I think we might be able to make the experience better 🙂command
in KubernetesRun job template”Marvin
12/09/2020, 3:15 PMClemens
12/09/2020, 3:15 PMjosh
12/09/2020, 3:16 PM