Quick question. we have people working on a shared server. I have written a workflow that runs locally under my env. But when my colleague tries to run the same workflow on the server, he got the following error

$ python tasks/run_workflow.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/pathlib.py", line 1284, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/flyte/20220422_220444/sandbox/local_flytekit'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/pathlib.py", line 1284, in mkdir
    self._accessor.mkdir(self, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/flyte/20220422_220444/sandbox'

During handling of the above exception, another exception occurred:
...
...
PermissionError: [Errno 13] Permission denied: '/tmp/flyte/20220422_220444'

How do I ensure reproducibility for different local environments?

@Han, can you share more details about your workflow? How are you running it? And how is your colleague running it?

We both work on the same shared server. We are both just doing

python run_workflow.py

from our user accounts on that server.

aah you mean shared-server for the local development?

Can you double check if your colleague has access to /tmp/flyte?

@Eduardo Apolinario (eapolinario) i think what happened is one of them first created

/tmp/flyte

and the second person cannot access it, as we restrict it to the uid only

Yes! It's a shared server for development (bare metal). I am guessing that I ran a workflow “locally”, and flyte setup local temp, but others don't have permissions. So when they try to run flyte workflow on their accounts they don't have access and get blocked.

No we will change this, if you can get by for a bit

Ok. Please keep me posted.

@Eduardo Apolinario (eapolinario) made a PR

@Han, can you give flytekit 1.0.0 a try?

Yes, lemme grab it