Hi, we have a bitbucket repo (let's call it repo-1) that needs to clone another private repo (repo-2). Actually it needs to do this via a pip install, but we have also tested via normal `git clone`.
We have tried both the `Pipeline | SSH Keys` setting (on repo-1) and then giving that public key access via the `User Access Keys` setting on repo-2, as well as doing our own key and making that available as environment var to the bitbucket pipeline in repo-1.
In the case of trying a simple git clone, both these fail:
<span>+ git clone <a href="mailto:git@bitbucket.org" target="_blank" rel="nofollow noopener noreferrer">git@bitbucket.org</a>:our-org/private-repo-2.git</span>
<span>Cloning into 'custos-video-client'...</span>
<span>ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory</span>
<span>Host key verification failed.</span>
<span>fatal: Could not read from remote repository.</span>
<span> </span>
It also looks like a password is expected for the private key, but afaik when using keys generated under `Pipeline | SSH Keys` setting, no passwords are involved?
Is there anything else we can look at, or perhaps some issues/constraints with accessing private bitbucket repos from a pipeline that we should be aware of?