In case anyone can help with this: I want to run a workflow that should use the latest available image as a base when running it. If I put

base_image={IMAGE_PATH:latest}

in the

image_spec

it'll use the latest at the time of registration, but then will be out of date. I've been playing with the

pod_template

, setting up a container with that image, but when I try this for some reason I get

ModuleNotFoundError: No module named {path.to.workflow}

I imagine you'll need more context, but let me know if at least this sounds like a reasonable approach and then I can post more context as required

Would this violate the flyte fundamentals, registration needs the sha256 right if it takes a latest tag then any historical runs when re-run will not be a valid rerun right what is the use case for this behavoir wouldnt just registering a new version suffice

It's a dynamic workflow that runs a task based on the input params. The task then runs a script from a specific commit (so the task git pulls that commit, then runs uv sync and then runs the script) The idea is to skip registering a new version so we can quickly iterate by changing the commit. This works fine, but the uv sync step can take a while, and it would take a lot less time if there was a way to have the dynamically launched task use a base image defined at run time (so either a base image based on the commit, or a very recent one)

i see, are you doing full registration or fast registrtaion

Fast registration

i see, is there a reason why you do uv sync everytime; unless you add packages to every commit it shouldnt really need to run all the time right

@little-jackal-69856 imagespec today does not recompute a diff. This is what you might be running into. With v2 we have fully changed imagespec to have layers built in. But our preference is to not have the same mutable base image. Otherwise layer caching breaks