containerImage don't have any impact without providing taskRunner about kestra

[loicmathieu]

This is by design, you either use the new taskRunner property that works with the containerImage property, or use the old runner property that works with the docker property.

You cannot mix both and I'm not sure it's a good idea to allow that as now there is a clear dichotomy: you either use one or the other facility.

[anna-geller]

1. When using containerImage without specifying taskRunner or runner, it uses the default Docker-type taskRunner
   
2. When using runner, user would need to use docker.image to set the image rather than containerImage

everything seems to work as expected