Hello everybody, I´ve played around with flyte on...
# ask-the-community
Hello everybody, I´ve played around with flyte on my local machine. Now I wanna run some simple (scheduled) workflows on my VPS. I am currently a little confused, on how to do that. Should I simply run a flyte demo cluster (
flyte demo start
) on my VPS?
you can certainly create a
flyte demo
cluster on your VPS and schedule workflows on there… @Yee @jeev is there any additional stuff to be aware of if you want to run a demo (sandbox) cluster in this fashion? you can also follow the single cluster deployment guide to create your own Flyte cluster (which cloud provider are you using?).
Thanks for the reply. My VPS is hosted by contabo.com. Additionally, I have a ARM virtual machine from oracles always free program. Can I run flyte on an ARM processor?
flyte demo start should get you up and going!
the demo sandbox runs on arm64 as well
installed flyte on my arm virtual machine and got the following error, when running the example from here https://docs.flyte.org/projects/cookbook/en/latest/index.html
Copy code
(flyte) ubuntu@instance-20230102-1221:~/dev/test_flyte$ pyflyte run example.py training_workflow \
    --hyperparameters '{"C": 0.1}'
Traceback (most recent call last):
  File "/home/ubuntu/mambaforge/envs/flyte/bin/pyflyte", line 5, in <module>
    from flytekit.clis.sdk_in_container.pyflyte import main
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/site-packages/flytekit/__init__.py", line 165, in <module>
    from flytekit.core.base_sql_task import SQLTask
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/site-packages/flytekit/core/base_sql_task.py", line 4, in <module>
    from flytekit.core.base_task import PythonTask, TaskMetadata
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/site-packages/flytekit/core/base_task.py", line 26, in <module>
    from flytekit.configuration import SerializationSettings
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/site-packages/flytekit/configuration/__init__.py", line 473, in <module>
    @dataclass(init=True, repr=True, eq=True, frozen=True)
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/dataclasses.py", line 1211, in wrap
    return _process_class(cls, init, repr, eq, order, unsafe_hash,
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/dataclasses.py", line 959, in _process_class
    cls_fields.append(_get_field(cls, name, type, kw_only))
  File "/home/ubuntu/mambaforge/envs/flyte/lib/python3.11/dataclasses.py", line 816, in _get_field
    raise ValueError(f'mutable default {type(f.default)} for field '
ValueError: mutable default <class 'flytekit.configuration.S3Config'> for field s3 is not allowed: use default_factory
i think that’s a python 3.11 issue. looks like we need some refactoring @Yee @Eduardo Apolinario (eapolinario) https://discuss.python.org/t/better-communicate-dataclass-mutable-default-check-change-in-python-3-11/19028
@Volker Lorrmann using python 3.10 for now will unblock
also worth noting that we're excluding python 3.11 in flytekit 1.3.2, while we work on https://github.com/flyteorg/flyte/issues/3312
Thanks. I´ll switch to python 3.10