Hi #C048ZHNT9QS - Does anybody have a reference to a Dockerfile with

prefecthq/prefect:2-latest

as base image, that they can run locally? I’m having hard time defining the

ENTRYPOINT

I don't have one on GitHub, but I could get one up pretty quickly. How do you want to use it locally? Knowing that will help ensure the entrypoint does what you need.

Hi Ryan, and thanks for a swift reply. I’m basically trying to build my own Docker Image (with my own pip requirements etc) and I was jus wondering if it possible to actually run that docker container locally, to test that it works 🙂

If you just want to test that it works, it might be easier to shell into it by running something like

docker run -it my_image:my_tag bash

. Then from the shell I believe you could run

python -c 'from listings.get_listings import run_pipeline; run_pipeline()'

This works!

FROM prefecthq/prefect:2-latest

WORKDIR /home/root/

COPY pip/requirements.txt pip/requirements.txt
RUN pip install -r pip/requirements.txt

COPY python/ python/
WORKDIR /home/root/python/src/main

ENTRYPOINT ["python", "-m", "listings.get_listings"]

That'll do it too, if your module runs your function instead of just defining it. Sounds like that's the case here 😄 Glad to hear that worked for you!

Great! So bonus question: What do I need to do now, in order to get my deployment to reference my own docker image?

It does! There are a couple of ways. The first is running the deployment CLI with the docker-container infrastructure type as shown here, and then editing the image name in the deployment YAML before deploying it. You'll also need to set the deployment path as well because if you are including your code in the docker image, Prefect will look for it under

/opt/prefect/flows

unless you tell it otherwise.

Hm, okay - I think it makes some sense 🙂 But perhaps I’m on the wrong path here? If I want to have my flow running in a docker container, my idea was to build the docker image, push it to ECR, pull it on the Agent machine and then somehow have Cloud start that docker container for me on the remote machine (Such as a small EC2 instance or something like that).

Got it - and I think you are on the right path! There's just one change I think you'll need to make from what I described if you want the container to start on a remote machine.

OK, that’s good news at least 🙂 Please help me understand what that change is? Do I need to specify something else for the ENTRYPOINT or completely leave it out?

We have another infrastructure block called ECSTask. It will run your Docker image using ECS for each flow it needs to run, backed by either EC2 or Fargate (whichever you prefer). Based on what you've mentioned here it sounds like this will accomplish what you need? Since you are using a Prefect base image, you should be able to leave the entrypoiny out and just inherit the base image entrypoint.

Jeesh, that is a lot to take in - looks really cool though 🙂 I do think the ECSTask is perhaps more what I need. Just a quick question: Would it be possible to pay either Anna or one of your colleagues to join us for a couple of hours, and help/teach us to get the basic level of understanding and infrastructure up and running? My guess is, that when you’ve done this right the first time, building next many pipelines will be a lot easier 🙂

It's definitely easier after you've set it all up it the first time! As to your question, I need to confer with a few of my colleagues to make sure I get you in touch with the right person to provide more information 🙂

just to add, no need to override the entrypoint, the default one from the Prefect image will work, other than that, nice work so far! as Ryan mentioned, we do have paid support helping you get onboarded cs@prefect.io and I can ask any ECS specific questions too

Hi @Ryan Peden and @Anna Geller - Thanks for getting back! OK I’ll reach out to your professional team. And thanks Anna for the input regarding the entrypoint 👌