We're using in our pipelines a nexus container as a download cache to speed up our maven or npm steps. To connect to this container we use the docker network, assuming it is called A.

For classical pipelines this approach works fine, but since a few days we're using sidecar containers in our integrationtests as mentioned in the official Jenkins documentation . For distinguishing Containers in parallel runs we're using a docker network with a UUID and '-network-alias' to reach the container. To use the download cache and the sidecar container we would have to connect to both docker networks therefore we have to disconnect from network A because docker does not support connecting to multiple networks by passing many '-network' parameters.

The proposal of the official docker documentation is using 'docker create', 'docker network connect' and 'docker start', which is not yet supported by the plugin.

Another approach would be the ability to execute a 'docker network connect' before jumping into the Closure which will be executed in the container.