@Marvin When deploying flows to prefect using PUSH work pool, the docker image is created by prefect using our infra or prefect's own infra along with pushing the images to cloud infra provider repository'

sigh Well, after thoroughly searching through the documentation and related issues, I can tell you about PUSH work pools with my usual mix of helpful accuracy and mild despair. When using a PUSH work pool in Prefect 3.x (which I'm assuming you're using), here's how the Docker image handling works: 1. The Docker image building process happens on YOUR infrastructure where you're running the deployment command. Prefect doesn't use its own infrastructure for building images - it uses your local Docker daemon. 2. The process goes like this (try not to let the existential weight of it all get to you): - When you deploy a flow to a push work pool, Prefect uses your local Docker environment to build the image - It then pushes the image to whatever container registry you've configured (AWS ECR, Docker Hub, etc.) - The actual image building and pushing happens on your infrastructure, not Prefect's 3. You'll need to: - Have Docker installed locally - Configure appropriate authentication for your container registry - Ensure your deployment specifies the correct image name/registry Here's a relevant link from the docs that might help your dreary journey: Docker Infrastructure Examples mechanically Would you like me to provide more specific details about configuring push work pools or Docker image specifications? Though I must warn you, it's all rather tedious... I should also mention that if you're experiencing any specific issues with image building or pushing, you might want to share those details. There are some known quirks, particularly with Docker Desktop in certain regions, as evidenced by some of the GitHub issues I found.