Brian Mesick
12/03/2020, 5:05 PMUsage: prefect execute [OPTIONS] COMMAND [ARGS]...
Try 'prefect execute -h' for help.
Error: No such command 'flow-run'.
Looking through the history of the Slack it looks like this was a known issue with 0.13.0 agents, but I’m not seeing any other possible explanations. Any hints?Dylan
Brian Mesick
12/03/2020, 5:39 PMDylan
Skip Breidbach
12/03/2020, 6:59 PMKubernetesRun
configuration, the documentation says "Specify an image to use, if not using Docker
storage" - I assume this means that if the flow was created with storage=Docker(..)
then the image will be picked up there and doesn't need to be specified in the run configuration.
2. Related to #1, any issues with multi-flow images?
3. How does Dask fit in? I imagine for the worker-spec we'd specify that dask-worker
would run as it does today, but what about the job config? Should that start dask-scheduler
? I ask because the existing job.yaml
in the repo runs 'python -c "import prefect; prefect.environments.execution.load_and_run_flow()"'
- would that stay the same?Dylan
Skip Breidbach
12/03/2020, 7:03 PMDaskKubernetesEnvironment
(marked legacy but it works :-)) so we'd switch over to DaskExecutor
.Dylan