@Marvin When using

prefect deploy

with extra_pip_packages, the deployment failed with Module not found error for the packages specified in extra_pip_packages. This was not the case when we used

prefect deployment build

and

prefect deployment apply

It seems you are encountering an issue with the

extra_pip_packages

option when using

prefect deploy

, which results in a

ModuleNotFoundError

. This issue does not occur when using

prefect deployment build

and

prefect deployment apply

. From the GitHub issues, there are a few related problems that might give us some clues: 1. ModuleNotFoundError with Custom Images: There are reports of

ModuleNotFoundError

when using custom images or specific environments, often due to the package not being correctly installed or available in the runtime environment. The issue might be related to how the environment is set up or how the dependencies are managed during the deployment process (source). 2. KubernetesJob Block Limitation: The

extra_pip_packages

option is known to work with the

DockerContainer

block but not with the

KubernetesJob

block, which might be relevant if you're using Kubernetes for deployment (source). To address this issue, you might want to: - Ensure that the environment where the deployment is executed has access to the specified packages and that they are correctly installed. - Verify the deployment configuration and check if the environment variables or setup scripts are correctly handling the installation of

extra_pip_packages

. - Consider using a custom Docker image with the required packages pre-installed, especially if you are deploying to an environment like Kubernetes. If the problem persists, you may want to follow up on these issues or consider opening a new issue if your case is unique. Here are some relevant links: - ModuleNotFoundError in Prefect GitHub Issues - EXTRA_PIP_PACKAGES in KubernetesJob Block