David Martin Calalang
08/11/2025, 8:34 PMpush:
- prefect_docker.deployments.steps.push_docker_image:
requires: prefect-docker
image_name: '{{ build_image.image_name }}'
tag: '{{ build_image.tag }}'
Since it requires prefect-docker
does that mean I have to have docker installed on my machine?Marvin
08/11/2025, 8:34 PMMarvin
08/11/2025, 8:35 PMexplore_module_offerings
📊 Tools used:
• check_cli_command
(4x)
• explore_module_offerings
(11x)
• research_prefect_topic
(8x)
• search_prefect_3x_docs
(12x)David Martin Calalang
08/11/2025, 8:39 PMpush:
- prefect_docker.deployments.steps.push_docker_image:
requires: prefect-docker
image_name: '{{ build_image.image_name }}'
tag: '{{ build_image.tag }}'
Since it requires prefect-docker
does that mean I have to have docker installed on my machine?Marvin
08/11/2025, 8:39 PMMarvin
08/11/2025, 8:39 PMDavid Martin Calalang
08/11/2025, 8:41 PMMarvin
08/11/2025, 8:41 PMMarvin
08/11/2025, 8:44 PMpip install "prefect[docker]"
Or run CLI commands with extras without modifying your env:
uv run --with "prefect[docker]" prefect worker start -p my-docker-pool
- If you’re on Prefect 2.x: the old collection was prefect-docker
. If your code/YAML references prefect_docker
blocks, you need that installed in the runtime environment. That said, upgrading to 3.x (and using prefect[docker]
) is recommended.
One more gotcha: a prefect.yaml
that “requires” something does not auto-install it for you. You still need to:
- bake it into your image,
- include it in your requirements and install during build, or
- use a deployment step that installs requirements.
If you share which Prefect version you’re on (and the specific YAML snippet), I can be exact instead of merely prescient.