In my opinion, this approach is the best fit for fulfilling my purpose at least. ssh directory (not secure huh!) and help from the great teacher Google found many solutions for me like Pass local machine’s SSH key to docker container, Using SSH keys inside docker container and so on, however honestly speaking I was not able to implement the ssh key pair copying idea (may not be tried so hard, because I found a better and safe idea later?)įinally took the idea of ssh agent forwarding (which method I used already in the vagrant based machine). My idea was to copy my local ssh key pair into container´s. The main reason for using ssh remote URL is to avoid entering username and password at each time of push, pull (required over https remote URL) Why SSH agent for docker containerįor me as a new macOS user, for the first time, I faced problem while trying to clone some of the repositories from the inside docker container. Beside in my current company (Zitelab ApS), we have our gitlab enterprise edition server which is hosted into our own cloud and most of the repositories are internally accessible by our team exclusively. #11 44.97 npm ERR! and the repository exists.I am used to git ssh remote URL, in case of public and private repositories either from GitHub or gitlab (those projects are either contributed or authored by me). #11 44.97 npm ERR! Please make sure you have the correct access rights #11 44.97 npm ERR! fatal: Could not read from remote repository. #11 44.97 npm ERR! command git -no-replace-objects ls-remote 44.97 npm ERR! Permission denied (publickey). #11 44.97 npm ERR! An unknown git error occurred However I get this error whenever I try to run docker-compose up #11 44.97 npm ERR! code 128 įollowing this article, inside the docker-compose.yml file I have included the $SSH_AUTH_SOCK like this: environment: When building the image with Dockerfile alone I pass the -ssh default argument, like this and it successfully installs the private repo: docker build -ssh default -t CONTAINER_NAME. Here's the part of Dockerfile where I use the BuildKit mount feature: RUN mkdir -p -m 0600 ~/.ssh & ssh-keyscan > ~/.ssh/known_hosts However I can't use the Dockerfile with docker-compose. When I create the docker image using the docker build command, the image is successfully created and everything works fine.

I am having issues using a private github repo in one of my NestJS apps.

Docker for mac ssh agent