-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudpickle error when base_image isn't specified #1698
Comments
@cicdw @wagoodman Do you think this could be due to cached layers? I haven't encountered this yet and I often don't provide a base image. |
@nanseay could you include what version of Python you are running? |
Yep, Python 3.7.3 |
We looked at this offline and it seems like it's an issue with assumptions on the Docker storage. If you provide that your https://github.com/PrefectHQ/prefect/blob/master/src/prefect/environments/storage/docker.py#L94 |
After more discussion, we think the best way forward is to always attempt to install the prefect package unless it is already installed. For example, regardless of the Additionally, it would be good to check if the user specified a |
Description
If you remove the base_image kwarg from storage and attempt to deploy a flow, a Cloudpickle error is triggered
Traceback (most recent call last):
File "/root/.prefect/healthcheck.py", line 12, in
import cloudpickle
ModuleNotFoundError: No module named 'cloudpickle'
Expected Behavior
No errors and flow deploys as expected (note: using kwarg base_image="prefecthq/prefect:0.7.0-3.7" allowed me to deploy my flow successfully)
Reproduction
Remove base_image kwarg from storage and deploy flow
Environment
Running Core 0.7.0
The text was updated successfully, but these errors were encountered: