There's no technical limitation to use this option (we actually already
support it to allow docker.sock bind mount on a dedicated side container),
but our experience is most user use this for bind-mount, which result in
permission issues and in most case are just short terms workarounds to
introduce bad practices. So we decided *not* to expose this option to
IIUC your use case (from some private email) some legacy jobs you run rely
on a NFS server to host project dependencies. Relying on a bind mount would
make your build fragile and non-reproducible. You better should create a
project specific docker image, to include those dependencies (assuming you
can't update your build script to a modern dependency resolution approach).
For sure this require some effort to migrate your builds, but I can't
consider "*legacy bad practice*" as a valid use-case :P
Le vendredi 14 octobre 2016 15:55:01 UTC+2, Qiang a écrit :
> How can I set container options to the Docker slave such as volume
> settings? I need to mount a host directory to the container.
> So far, the only option I can see is to define the slave container image,
> and side container image as following:
> dockerNode(image: "maven:3.3.3-jdk-8", sideContainers:
> How do I pass "-v" or "--volumes-from" to the slave container?
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.