# Bug fix: git cloning another repository within Renku session

**URL:** <https://renku.discourse.group/t/bug-fix-git-cloning-another-repository-within-renku-session/465>\
**Category:** RenkuLab\
**Created:** [29 October 2021 11:48 UTC](https://renku.discourse.group/t/bug-fix-git-cloning-another-repository-within-renku-session/465 "2021-10-29T11:48:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gavin-k-lee](https://yyz2.discourse-cdn.com/free1/user_avatar/renku.discourse.group/gavin-k-lee/32/233_2.png) [@gavin-k-lee](https://renku.discourse.group/u/gavin-k-lee)\
**Post date:** [29 October 2021 11:48 UTC](https://renku.discourse.group/t/bug-fix-git-cloning-another-repository-within-renku-session/465/1 "2021-10-29T11:48:10Z")

</div>

Dear users,

We would like to alert you of a bug that we have noticed in interactive sessions which may affect you. When inside a Renku project in an interactive session, running `git clone` on another project through HTTPS will fail with an error like this:

```auto
fatal: unable to access 'https://renkulab.io/gitlab/some.user/some-project.git/': server certificate verification failed. CAfile: none CRLfile: none

```

We are in the process of upgrading our base Docker images (see [Fix image build and bump base image version by ableuler · Pull Request #197 · SwissDataScienceCenter/renkulab-docker · GitHub](https://github.com/SwissDataScienceCenter/renkulab-docker/pull/197)), however since this will take a little time, here is a quick fix: Add the following lines to your project’s Dockerfile:

```auto
USER root
RUN apt-get update && apt-get upgrade -y curl
USER ${NB_USER}

```

Note that this bug affects git submodules as well.

Please let us know if you encounter problems with the quick fix!