-
Task
-
Resolution: Unresolved
-
Major
-
None
If a pipeline defines a agent { docker{ ... }}}} section, the plugin will rely that docker cli is installed on the node to perform the appropriate operations ({{{}docker inspect, docker run, ...)
When using Jenkins in a container, this means we need to install docker-in-docker, which brings extra complexity.
If docker-build-step-plugin already brings a dependency to docker-java (if I understand JENKINS-22985 right), maybe the same could be done for this plugin too ?
[JENKINS-69852] Use docker-java instead of docker cli
Description |
Original:
If a pipeline defines a {{agent \{ docker { ... } }}} section, the plugin will rely that docker cli is installed on the node to perform the appropriate operations ({{{}docker inspect{}}}, {{{}docker run{}}}, ...)
When using Jenkins in a container, this means we need to install [docker-in-docker|https://hackmamba.io/blog/2022/04/running-docker-in-a-jenkins-container/], which brings extra complexity. If {{docker-build-step-plugin}} already brings a dependency to docker-java (if I understand |
New:
If a pipeline defines a {{agent \{ docker{ ... }}}} section, the plugin will rely that docker cli is installed on the node to perform the appropriate operations ({{{}docker inspect{}}}, {{{}docker run{}}}, ...)
When using Jenkins in a container, this means we need to install [docker-in-docker|https://hackmamba.io/blog/2022/04/running-docker-in-a-jenkins-container/], which brings extra complexity. If {{docker-build-step-plugin}} already brings a dependency to docker-java (if I understand |