Hi Chad, Thanks for your response. I am not able to clone repository even manually even if i am only using docker-dind-21.4 version without adding anything from docker file. Ye we are mounting repository access key to the image and I can see these file available in .ssh directory. But when I am trying to clone it always failing with error “permission denied (publickey)”. I have permission in both working and non working images and both are same.
I don’t see any log folder creating inside godata. Regards Sachin > On 15 Jan 2022, at 1:14 PM, Chad Wilson <[email protected]> wrote: > > > Hi Sachin > > Can you share your custom Dockerfile (partially redacted if necessary), and > any volume/bind mounts you might be using on your custom agent image? > > It's possible that something you have in your setup is not playing nicely > with Alpine 3.15 or git 2.34.1, which the docker-dind images are based on. > There are no other major changes between the versions that come to mind as > possibly causing a problem. > > Other than that perhaps you can share some lower level logs of what is going > wrong, e.g start a container and try a clone without the agent actually > running and see if you can replicate the same problem and we know why the > clones are failing. > > e.g replace with your container below > > docker run -it --entrypoint '' -e GIT_TRACE=1 <my-custom-agent-image> bash > cd /tmp > git clone <somerepo> > > If that is not showing the problem, perhaps you can look at and share any > other detail in /godata/logs/go-agent.log from running the real GoCD agent. > > -Chad > > PS: GoCD agents still bootstrap their core code from the server at > startup/registration, so it's really just the bootstrap logic and underlying > OS image that is running the "old" version. Good to update them to pull in > OS-level patches, tool patches/fixes and agent bootstrapper fixes, but > shouldn't cause an overall stability issue. > >> On Sat, Jan 15, 2022 at 10:29 AM Sachin Gupta <[email protected]> >> wrote: >> Hi Team , >> >> I have updated gocd server and agent to version 21.4 but after that agent >> always failed to do git clone while running pipelines. >> >> I have used docker-dind gocd image version 21.4 to create gocd agent image. >> Agent start working again if I use back my previous agent image which was >> created using docker-dind gocd version 21.3. >> >> So in my current situation my gocd server running on version 21.4 but agent >> are still using docker-dind version 21.3. >> >> Any suggestions to resolve this and to use latest gocd server and gocd agent >> image version 21.4 together. >> >> Regards >> Sachin >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/84BA0143-63CB-4EA9-A4E6-B5ABE98426B4%40gmail.com.
