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

Flyte

I am trying to override the base container image that a task is using to not inherit from the parent workflow that is calling it, using
```.with_overrides(
   container_image=base_container_image_url_str
)```
is not working. I have access to the base container url string. Any ideas here? I cant seem to get the image to update and have looked into `ImageSpec` but cant seem to get that working at the moment.

Is there a way to set this in the `@task(task_config=...)` ?

`@task` itself has a `container_image` arg, can you use this one? You can pass a string.

<https://docs.flyte.org/projects/cookbook/en/v0.3.66/auto/core/containerization/multi_images.html>

This page might be helpful :slightly_smiling_face:

I have tried calling the function with
```@task(
    container_image="&lt;container image url"
)```
but have not been successful. Would running this in `map_task` affect this at all?

I am able to pull the URL for the image, log it to confirm that I am setting it, but cannot seem to get it to apply.

I can’t say whether map task has an effect here :thinking_face:

Hmmmm, yeah I can try to remove map_task and try this without it, however I really cant move away from my final implementation needing to use it.

<https://docs.flyte.org/projects/cookbook/en/v0.3.66/auto/core/containerization/multi_images.html#:~:text=Any%20one%20of%20the%20following%20is%20an%20acceptable|Here> it says this:

```Image reference is specified, but the version is derived from the default images version container_image="<http://docker.io/redis:{{.image.default.version}}|docker.io/redis:{{.image.default.version}}>,

Both the FQN and the version are derived from the default image container_image="{{.image.default.fqn}}:spark-{{.image.default.version}},

The images themselves are parameterizable in the config in the following format:
{{.image.&lt;name&gt;.&lt;attribute&gt;}}```

Wondering whether having a var `{{..`  is actually required.

But I would also first try without map task to rule it out this has any effect.

could it be that this format `{{.image.&lt;name&gt;.&lt;attribute&gt;}}` doesn’t support digest `&lt;image_name&gt;@sha256:&lt;hash&gt;`?

It seems that `@task(container_image=&lt;image_name&gt;@sha256:&lt;hash&gt;)` works however. I think it could be useful to support digest in `map_task`’s `with_overrides` as well since digest is more specific. Can it be added to the roadmap?

<@U04UNGML8NB>, currently it doesn't support that <https://github.com/flyteorg/flytekit/blob/master/flytekit/core/python_auto_container.py#L305|format>. Mind opening a gh issue?

<@U051JAF2XCP>, from the thread it's not clear if this is the issue you're seeing.