Hey team - if we're switching between image reposi...
# ask-metaflow
g
Hey team - if we're switching between image repositories (private within our cloud and public docker hub) is it best to not set
METAFLOW_DEFAULT_CONTAINER_REGISTRY
within our config or set it to empty string so that within in each flow we can specify the full image path to pass into
@batch
?
1
a
totally depends on your use case. the image specified within
@batch
takes precedence over the image specified as a default in the config.
g
That's good but it seems whatever is in
METAFLOW_DEFAULT_CONTAINER_REGISTRY
gets prepended to whatever is specified in
@batch
which means if we have different repos we want to look at and specify a default via config, that default is always going to get prepended, no?
a
in
@batch
you can define the full path to the image which will ensure that
METAFLOW_DEFAULT_CONTAINER_REGISTRY
is ignored in that case
g
Excellent. Didn't know if would ignore if a full path is provided.
among us party 1