I believe I found the answer. I will need to create my own image using the docker gocd agent image as the base. In my image, I will need to install whatever tools I need for my builds. As for docker, I'll need to install the docker binaries and volume mount the host machine's docker socket so that the gocd agent container can create sibling docker images on the host machine.
On Thursday, December 7, 2017 at 3:56:03 PM UTC-5, Aver wrote: > > Hi, > > I'm new to go-cd. I'm trying it out right now to see how it fits in my > environment/use-cases. > > I want to use dockerized go-cd server and agent. I have this part working. > Dockerized server and agent is setup on 2 separate hosts and they are > connected/communicating successfully. I have some requirements that I'm not > sure how to tackle. > > Dockerized go-cd agent comes with openjdk8 pre-installed. For my pipeline > to compile/build my code base, they need a different JDK and also some > other applications (i.e. eclipse). If I have those pre-requisites installed > on the host machine that is running go-cd agent as a docker container, will > it work? I suspect it won't because the agent won't be able to use anything > that is not in the container. Has anyone done something similar already? > > I also need to build docker image. My build script already has necessary > code that can compile source codes and then do a docker build. But, if I'm > running go-cd agent as a docker container, how will it handle docker > commands? Has anyone used dockerized agent for building docker image as > part of the pipeline? > > Is dockerized agent the right approach based on what I listed above? > Appreciate any help/pointers you can provide. > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
