When using the builder to create a new container image, we used to default on using the docker command for everything.
While this is simple, this can limit what users try to do with the plugin, typically if they need to run their builds on a specific version of Docker which they built from scratch and won't install it, or if they want to build with a Docker-compatible alternative like podman.
To circumvent this limitation, we add a new docker_path option to the builder, so they can use this to use alternative docker binaries for orchestrating their builds with.
When using the builder to create a new container image, we used to default on using the
dockercommand for everything.While this is simple, this can limit what users try to do with the plugin, typically if they need to run their builds on a specific version of Docker which they built from scratch and won't install it, or if they want to build with a Docker-compatible alternative like
podman.To circumvent this limitation, we add a new
docker_pathoption to the builder, so they can use this to use alternative docker binaries for orchestrating their builds with.