Re: [go-cd] GOCD restart issue

Did someone recently change something in your compose volume mounts? It's probably not a good idea to mount things directly into /go-working-dir like the line "*- ./gocd/docker-elastic-agents-3.2.3-415.jar:/go-working-dir/plugins/external* " The container entrypoint expects to own and manage

Re: [go-cd] GOCD restart issue

its is just regular container in linux server and used local disk for volume On Tuesday, May 7, 2024 at 9:18:37 PM UTC+5:30 Vijayakumaran A. wrote: > We have started container using docker start servicename. > > Here is the composer file of gocd server part > > server: > container_name:

Re: [go-cd] GOCD restart issue

We have started container using docker start servicename. Here is the composer file of gocd server part server: container_name: gocd-server image: gocd/gocd-server:v23.4.0 restart: always ports: - "8153:8153" volumes: - ./gocd/data:/godata -

Re: [go-cd] Mount .ssh from EFS to the container (from the image gocd/gocd-server:v22.3.0)

To add onto the many options here, if you only need the SSH keys to be used by Git for clones etc, you can entirely customise how GIT uses SSH using the *GIT_SSH_COMMAND* env var ; set at the container level.

Re: [go-cd] Mount .ssh from EFS to the container (from the image gocd/gocd-server:v22.3.0)

On Mon, May 6, 2024 at 3:30 AM Jason Smyth wrote: > Hi Satya, > > A possible workaround to the limitation is updating the server image and > adding a symlink that points ~/.ssh/ to wherever you want to actually mount > the data. > > I have never experimented with using a symlink for the .ssh