Re: Docker vs Docker-compose with Jenkins

2016-11-24 Thread Baptiste Mathus
IIUC this is not a Jenkins issue but a Docker one. You should apparently look at volumes (create a named volume and share it between containers, don't use bind mounts/the host fs directly). Also, don't know mongo, but are you really directly accessing the db data?! Shouldn't you through a socket

Re: Docker vs Docker-compose with Jenkins

2016-11-24 Thread 'Peter Teichner' via Jenkins Users
Hi! Thanks for coming back to me: My difficulty comes from the complexity of the different software components. So for example I have the application container that needs to talk to the mongo container. And the reason I used bind mount is so the maven image can resolve the application by it's

Re: Docker vs Docker-compose with Jenkins

2016-11-23 Thread Baptiste Mathus
Ah bind-mounts... FWIW, as a general rule, bind-mounts should be avoided as much as possible, though using them especially for local dev & CI usage is indeed a pretty common hack (or for special things like TZ configuration where you mount the host file [in ro]). Depending on how you're using

Docker vs Docker-compose with Jenkins

2016-11-21 Thread 'Peter Teichner' via Jenkins Users
Hi All, I'm slightly unsure whether the topic is more suitable here or on Docker forums - anyway I decided to post it here. I have a pipeline whereby I have a job to build my Docker images using the Docker cloud plugin ( building 2-3 images at a time, application, db, proxy) In a separate job