Specify container image programatically

[flybd5]

What feature do you want to see added?

On standard nodes, a pipeline can programmatically specify which Docker container to run. It would be very useful for pipelines to be able do the same with Cloud Nodes, especially in Admin-restricted environments where the admin is forced to create a cloud node template for every container users would like to use.

Upstream changes

No response

Are you interested in contributing this feature?

No response

[MarkEWaite]

This is counter to the design of the docker plugin. It expects that the interface between the user and the cloud agents is done through labels. Shifting the burden for container definition onto the consumer of the container feels like the wrong direction for this plugin.

[flybd5]

Nobody is asking anyone to "shift the burden" to anything. Those words are nowhere in my enhancement request. The enhancement request is for the ability to allow the consumer to programmatically specify which container the cloud agent should run, instead of having to hard-code it in the definition of the agent. The Docker Plugin after all is nothing more than an interface to the Docker host's API. The Docker Pipeline plugin has allowed this from day one.

[elupus]

I think what flybd5 is asking for is to allow a configuration box in the cloud config dialog where the Dockerfile content can be specified instead of pre-built image. I'm sort of looking for that too, we don't have any internal docker hub.

I'd like to either pull a git repo with the Docker image definition, and build that before starting the agent.

[flybd5]

No, I mean dynamically specify the image and tag and have that pulled from the repo at runtime, and not be forced to predefine it. The dockerfile pull could help as well but it uses more resources while building the image.

[elupus]

Ok, then i misunderstood. Docker in docker might make sense for that. But yeah that is less nice.

[hshibuya-dd]

I have a different use case for this. I like to test new docker image in my pipeline without disturbing other developer's builds.
It will be nice if I can have job parameter IMAGE_TAG, which defaults to "latest", and in agent configuration, I can specify
the image using this parameter such as "my-repo/my-image:${IMAGE_TAG}". Then, for my test image, I can tag it as :pr-1234,
then run the PR pipeline with IMAGE_TAG: pr-1234.