#Dagger run parameter --workdir seems to be ignored?

1 messages · Page 1 of 1 (latest)

clear cedar
#

The results of .entries() on both dagger run python test.py --workdir ../ and dagger run python test.py are identical but shouldn't be - is this option still available? The docs suggest this option is still available and can accept a relative path?

lavish spire
#

@clear cedar try settting --workdir before python ? since otherwise --workdir will get passed to your pipeline and not the dagger CLI

clear cedar
#

I've tried both dagger run python --workdir ../../ test.py (--workdir isn't a valid argument for python) and dagger run --workdir ../../ python test.py and they both fail (value is ignored, looks for test.py in current dir, not workdir)

#

Oh hang on, I'll need to pass the dir in both workdir and for the file path right

#

Yep, that's it

clear cedar
#

Brain is having a slow day, thanks @lavish spire

lavish spire
#

haha, np!

#

🤣