acoustic-carpenter-78188
04/18/2026, 6:02 PMpyflyte run --remote command but does not mention that FLYTE_IMAGE_REGISTRY must be set when the workflow uses ImageSpec. The default project template (basic-template-imagespec) reads this variable to determine where to push the container image. Without it, task execution fails with:
KeyError: 'FLYTE_IMAGE_REGISTRY'
The working command is:
FLYTE_IMAGE_REGISTRY=localhost:30000 pyflyte run --env FLYTE_IMAGE_REGISTRY=localhost:30000 --remote ...
What changes were proposed in this pull request?
In `docs/user_guide/getting_started_with_workflow_development/running_a_workflow_locally.md`:
• Added step 6: export FLYTE_IMAGE_REGISTRY=localhost:30000 with a note explaining why the demo cluster registry is needed.
• Updated the pyflyte run command (now step 7) to include --env FLYTE_IMAGE_REGISTRY=localhost:30000 so task containers also have access to the variable.
• Fixed a pre-existing step numbering error where the steps jumped from 4 back to 3.
How was this patch tested?
Documentation change only; verified by reading the rendered diff.
Labels
• fixed
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
flyteorg/flyteacoustic-carpenter-78188
05/16/2026, 1:29 AM