Hello Team, Has anyone had a chance to test/investigate packaging a Flow with multiple .py files (or in hierarchical package structure) to be executed in Docker Storage? I’m trying to avoid adding extra parameters to the Docker Storage when writing a flow; I’d rather have my Flow packaged up as a python package and copied to the docker image which will later used by Prefect to execute the Flow.

with Flow("Example-Flow",
	storage=Docker(
			image_name="example_flow_import",
			image_tag="dev",
			dockerfile="<path/to/dockerfile>",
			python_dependencies=["numpy", "pandas"],
			files={}, # Trying to avoid this
			env_vars={}, # Trying to avoid this
		)) as flow:

Hey @Mehdi Nazari, I have a demo of a Python package added to the Docker file here. I think this might help.

Thanks @Kevin Kho, So looking at the code, it appears it is possible to have a Local Agent run a docker image as an isolated execution environment for the flow? In other words, I don’t necessarily have to bring up a Docker Agent for a docker image to be able to execute?

The Storage is

Local

but the RunConfig is

DockerRun

, which makes the file paths relative to the container. This would still use the Docker Agent as opposed to the Local Agent to spin up the container.

I’m getting an error testing your code; Do I need to install the python package on my local env in order for it to be registered?

What is your error? I guess that would help if you are running into import issues.

Yeah import issues I belive; this was after

prefect register

i think this will go away if you register from the project root.

python workflow/flow.py

Still there…

Oh sorry missed this. You could

pip install -e .

the package to install it. What IDE are you using?