https://prefect.io logo
j

Jake

01/26/2022, 8:02 PM
Hi everyone, I’m running into this error:
Copy code
Failed to load and execute Flow's environment: FlowStorageError('An error occurred while unpickling the flow:\n  ModuleNotFoundError("No module named \'cfmeta\'",)\nThis may be due to one of the following version mismatches between the flow build and execution environments:\n  - python: (flow built with \'3.6.15\', currently running with \'3.6.8\')\nThis also may be due to a missing Python module in your current environment. Please ensure you have all required flow dependencies installed.',)
I see that it is common and I read this thread. However, our flow needs to use specifically 3.6.15 because some of our dependencies require it and I do not see an agent that matches this version. I saw that script based storage was suggested, but we generate our flows dynamically so that is not an option. Any suggestions on how to resolve this? Thanks in advance!
a

Anna Geller

01/26/2022, 8:09 PM
Why is script storage not an option when you generate your flows dynamically? Can you explain? Based on the problem you’ve described I think that script storage seems like the best option. Also, can you share your storage and run configuration? or the entire flow definition? you can redact for privacy or DM me your flow
j

Jake

01/26/2022, 8:15 PM
Maybe I’m not understanding this well enough but the flows are composed across a couple different files. There isn’t a single flow file that can be uploaded. • s3 pickle based storage • kubernetes run with the image we are using
a

Anna Geller

01/26/2022, 8:18 PM
it looks like you could package your flow’s dependencies into a Docker image, provide this image to your KubernetesRun run_config and then just use script based S3 storage. I have an example that shows how this works: example
👀 1
alternatively, perhaps Docker storage would be an option for you? it would be capable of combining both your flow code and all dependencies and packaging those into a single Docker image that could be used by your Kubernetes agent
2 Views