Hi, I'm using a SSH-communicating, dynamically provisioned docker-plugin-cloud which uses the mounted docker.sock of the parent to spawn postgresql/wildfly containers in the pipeline as needed. Is there any way of using dynamic names/ports so that multiple slaves don't cause container name collisions (all using the parent docker dock)? Of course, using docker-in-docker would give the containers separate namespaces but apparently it has some downsides, too. Another approach could be to use scripting to determine a free container name/port from the docker.sock but that would leave the complication of the appserver datasource being hardcoded to some postgresql container etc.
How have you solved this? Thanks in advance, Nik -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4aa3be43-cb1d-4ddf-ab98-7fd62885d437%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
