My role involves creating containers for nodejs projects. Within these projects, I utilize a private repository and require access to it. To achieve this, I have implemented the following Dockerfile:
FROM node:15
RUN echo "StrictHostKeyChecking no" >> /etc/ssh/ssh_config
RUN mkdir -p -m 0600 ~/.ssh && ssh-keyscan bitbucket.org >> ~/.ssh/known_hosts
COPY keys/ssh_config /root/.ssh/config
COPY keys/bitbucket /root/.ssh/bitbucket
RUN chmod 600 /root/.ssh/bitbucket
RUN npm install -g typescript ts-node
WORKDIR /var/www
EXPOSE 3000
The contents of the ssh_config file are as follows:
Host bitbucket.org
IdentityFile /root/.ssh/bitbucket
StrictHostKeyChecking no
In addition to this setup, I have modified my package.json with the following line:
"my-interfaces": "git+ssh://bitbucket.org:MY_USER_NAME/my-interfaces.git#master",
Upon building the container through docker-compose and attempting to run npm i within the container, I encountered the following error message:
npm ERR! code 128
npm ERR! command failed
npm ERR! command git ls-remote ssh://<a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="e0878994a08289948295838b8594ce8f9287">[email protected]</a>/MY_USER_NAME/my-interfaces.git
npm ERR! Permission denied (publickey).
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-04-30T08_19_38_999Z-debug.log
I also attempted an alternative approach by generating an SSH key within the container and adding the public key to bitbucket. However, this method resulted in the same error message.