I am trying to override the base container image t...
# ask-the-community
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
Copy code
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
but cant seem to get that working at the moment. Is there a way to set this in the
itself has a
arg, can you use this one? You can pass a string.
This page might be helpful 🙂
I have tried calling the function with
Copy code
    container_image="<container image url"
but have not been successful. Would running this in
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 🤔
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.
Here it says this:
Copy code
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:
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.
@Xinzhou Liu fyi
could it be that this format
doesn’t support digest
@Fabio Grätz @Ketan (kumare3) any ideas ^
I think it may not support that
got it thanks
It seems that
works however. I think it could be useful to support digest in `map_task`’s
as well since digest is more specific. Can it be added to the roadmap?
cc @Eduardo Apolinario (eapolinario)
@Xinzhou Liu, currently it doesn't support that format. Mind opening a gh issue? @Nicholas Roberson, from the thread it's not clear if this is the issue you're seeing.