https://flyte.org logo
#ask-the-community
Title
# ask-the-community
s

Sam Eckert

01/29/2023, 12:16 AM
I'm seeing weird behavior where workflows I deploy with
-d staging
are still being registered to the
development
domain. I feel like I'm missing something basic. This workflow has been running in
development
. I'm thinking maybe that workflows/launchplans can't be re-registered in a new domain? CMD:
/usr/bin/pyflyte register -p flytetester -d staging -i <image> atomwise/examples/flyte/
Some output:
Copy code
Running pyflyte register from /app/atomwise/examples/flyte/canonicalize_smiles_py_image.binary.runfiles/__main__ with images ImageConfig(default_image=Image(name='default', fqn='<account>/flyte_canonicalize_smiles', tag='<tag>'), images=[Image(name='default', fqn='<account>/flyte_canonicalize_smiles', tag='<tag>')]) and image destination folder staging on 1 package(s) ('/app/atomwise/examples/flyte/canonicalize_smiles_py_image.binary.runfiles/__main__/atomwise/exmples/flyte',)
b

Bernhard Stadlbauer

01/29/2023, 10:17 AM
Hi Sam! Which version of
flytekit
are you on? You should be able to print this using
python -c "import flytekit;print(flytekit.__version__)"
In case your version is
<1.3.0
, would you mind trying
--domain
instead of
-d
? I think
-d
was overloaded before with
--destination-dir
(changelog)
s

Sam Eckert

01/29/2023, 5:54 PM
That is absolutely it thanks! I'm on 1.2.7. I had been wondering about that -- my docker image creates an empty dir at
development/
because I was seeing errors where that directory was missing. Turns out I was just setting the
--destination-dir
flag haha
b

Bernhard Stadlbauer

01/29/2023, 5:54 PM
You’re welcome!
73 Views