Hi I am attempting to run go-cd in a Docker container using: https://hub.docker.com/r/gocd/gocd-server/
I recognize that this image is explicitly warning that it is not production ready. Mounting the data/config volumes is easy enough, however adding an SSL Certificate is posing a challenge: I have followed the instructions here: https://docs.go.cd/current/installation/ssl_tls/custom_certificate.html to create the correct keystore. I have also tested it in a non-dockerised deployment of go-cd and it works fine. When go-cd starts up it appears to always auto-generate a self-signed SSL Cert and copies it to /etc/go This means that to install a different signed SSL cert we need to wait until the server is up, then shut it down, then copy over the new keystore and replace and then start go-cd back up. This indeed works fine and now I am served with a signed cert. Is there a way to turn the auto generation off so that I can ADD the keystore from the Dockerfile on build and not have it overwritten? I have managed to ADD in the keystore at image build and call it something else, then using the 'docker exec' commands I have been able to stop the server in the running container, copy keystore, restart and that then gets me to the place I want to be: a go-cd server in a docker container with signed SSL. Any help or advice on how to solve this elegantly would be most appreciated. Thanks Hugh -- 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.
