Hey Prefect Community, I'm having a issue with running a deployment using a docker container. When I run the flow I deployed into a S3 bucket (other deployments using this bucket are working), I get the following error:

Flow could not be retrieved from deployment. Traceback (most recent call last): File "<frozen importlib._bootstrap_external>", line 879, in exec_module File "<frozen importlib._bootstrap_external>", line 1016, in get_code File "<frozen importlib._bootstrap_external>", line 1073, in get_data FileNotFoundError: [Errno 2] No such file or directory: '/opt/flow-code.py' The above exception was the direct cause of the following exception: ScriptError: Script at 'flow-code.py' encountered an exception: FileNotFoundError(2, 'No such file or directory')

Has anyone seen this before? Any tips on where to spend time troubleshooting?

How are you deploying?

Via command line using prefect deployment build command

Hey Mike! It's hard to know exactly but we have been experimenting with some more explicit and transparent mechanics for deployments in the form of "projects"; I've seen good success with users who transition to the project structure get away from these issues: https://docs.prefect.io/latest/tutorials/projects/ In your case, you're probably going to want to use the

docker-s3

recipe (

prefect project init --recipe docker-s3

)

Hmmm how hard is it to use the new Project way? I have some deadlines and I don't have much time to experiment with something new

I’ve seen that issue above when there was a conflict due to the version of the fsspec library and the remote storage library you are using (s3fs)

it shouldn't be hard, the biggest change would probably be that you'll need to use a worker instead of an agent (but assuming you have a standard setup it shouldn't be more than a new CLI command to start things). I'd say try Abhinav's suggestion (they're knowledgeable here so probably are on the right track!), and if you want to spend ~15 minutes with the new project structure that should be sufficient to get things working, but obviously no pressure if you solve it in other ways

OK thanks Chris and Abhinav. I'll try the version path first! Appreciate the guidance

Hello, it's kind of weird to have to downgrade s3fs and fssspect versions in order to not have an error when flows are running. I understand the project proposition, but what you did is a pretty major breaking changes and it's preventing us to upgrade without completely changing the way we deploy flow. Could you point us to what is actually causing the script not being able to pickup the file properly from s3?

FileNotFoundError: [Errno 2] No such file or directory: 'prefect2/test.py'

file is actually in S3, so it's probably a change in the way you handle paths with the S3 storage right ?

Hi Jean - projects have not affected or altered how previous deployments work so this isn't projects related; the s3fs / fsspec issue is an issue with those libraries which are libraries Prefect uses to upload / download code from S3

I tried updating s3fs to the same version as fsspec and it was not working. I'll try digging more. Any documentation on what s3fs version should be use with the latest prefect version ?

I haven't experienced this issue myself so am not sure what versions cause it - two things to confirm: • have you confirmed that these package versions are also the ones present in your deployment's runtime environment? • what block type are you using? you'll want to make sure to use

prefect.filesystems.S3

prefect 2.10.6 depends on fsspec!=2023.3.0 and >=2022.5.0

Apologies for not seeing this yesterday - that's interesting and seems like a potentially simple fix for a number of open issues; thank you for following through on investigating this! I'll review those issues and try to confirm this wouldn't have any adverse behavior

thanks!