Thanks for the pointer but as you said, I think that will be overkill for a team of a few developers.
I think I'll write a small utility that uses the Docker API for getting some free ports and then modify the involved components with parameters etc so that they can find each other. On Thursday, May 24, 2018 at 10:16:20 PM UTC+3, [email protected] wrote: > > You might need to move to a Container orchestration platform (Mesos, > Kubernetes, Swarm) for that, this would address all our needs, although it > is probably overkill! > > > On Thursday, 24 May 2018 13:55:23 UTC+2, Nicklas Karlsson wrote: >> >> 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/ad9aee74-2a3d-44b0-bfc1-2b2c1717cdea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
