https://flyte.org
Join Slack
Hi team :wave: – wondering what options are available for overriding the default `image_config` when...
# flyte-support
g
Hi team 👋 – wondering what options are available for overriding the default 
image_config
when using pyflyte – ideally via environment variable like 
FLYTE_INTERNAL_IMAGE
or 
~/.flyte/config.yaml
. In particular, when running
Copy code
pyflyte --verbose run --remote hello-world/example.py hello_world_wf

Running example.hello_world_wf with ...
image_config=ImageConfig(default_image=Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.9-1.10.2'), ...
This is for a bare-bones workflow
Copy code
from flytekit import task, workflow

@task
def say_hello(name: str) -> str:
    return f"Hello, {name}!"

@workflow
def hello_world_wf(name: str = 'world') -> str:
    res = say_hello(name=name)
    return res
I'd expect when 
FLYTE_INTERNAL_IMAGE=foo
then the above command would run using 
foo
as the image. Digging into the code https://github.com/flyteorg/flytekit/blob/e394af0be9f904fbf8be675eaa8b8cdc24311ced/flytekit/configuration/__init__.py#L287-L290 it looks like 
FLYTE_INTERNAL_IMAGE
never gets looked at and it runs using the flyte.org image instead
we'd like to override this via env var or config.yaml, so that it does not need to be manually passed in CLI via 
--image
every time
p
you can take a look at pod templates, which should expose a property allowing you to set the image value
g
drafted a quick PR to give a particular idea of what my concern/question is https://github.com/flyteorg/flytekit/pull/2223/files
cc @tall-lock-23197 thanks for the question here, just responded!
4 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by