The know issue
SSL Certificate problem: unable to get local issuer .... shows up when I try to import from a git repo that is signed with letsencrypt certs.
From this topic https://confluence.atlassian.com/bitbucketserverkb/ssl-certificate-problem-unable-to-get-local-issuer-certificate-816521128.html ... I try update the git inside the container, but with no success. I also searched for any other instance of git inside the container and configured them as well but still with no success.
Can someone suggest the correct way to configure the git service from the docker container?
Hello Florin
You may take a look at the external resources below in order to upgrade git in a docker container:
* Update Git version
* git-server-docker
As a workaround, you may want to try the options mentioned in the git client mentioned on the SSL certificate problem KB?
Regards
Rodrigo
Hi Rodrigo,
As an update on this, I did import them manually. I was able to set up git client to ignore the certificate validation on multiple versions of VM's ( not containers ),
The steps were:
Create a new project with the same name in bitbucket (for simplicity). make sure you have the same keys registered in both servers.
git config --global http.sslVerify false
git clone ssh://git@[old-git-domain]/[project]/[git-project-name].git
git remote add bitbucket ssh://git@bitbucket.domain.com]/[project]/[same-git-project-name].git
git push bitbucket
I believe the same process would be done from inside the container, as I can see in the logs that is trying to connect to the server and fails with the the error present in the ticket.
I suggest to still keep the question up as the solutions are not for the bitbucket container.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.