Loading github credentials about docker-lambda HOT 14 CLOSED

Putting them in /root/.ssh on the container should work. Something like this might work:

docker run -v "$PWD":/var/task -v "$HOME/.ssh":/root/.ssh lambci/lambda:build-nodejs4.3 npm install

You can play around manually in the container and see what works:

docker run -it lambci/lambda:build-nodejs4.3 bash

Or this if you want to expose your own .ssh directory in the container:

docker run -v "$HOME/.ssh":/root/.ssh -it lambci/lambda:build-nodejs4.3 bash

from docker-lambda.

Wow so helpful thank you! @mhart

from docker-lambda.

@pierrerappolt no probs, did that solve your problem?

from docker-lambda.

I'm getting this error at the moment

npm ERR! /root/.ssh/config: line 2: Bad configuration option: addkeystoagent
npm ERR! /root/.ssh/config: line 3: Bad configuration option: usekeychain
npm ERR! /root/.ssh/config: terminating, 2 bad configuration options

from docker-lambda.

I tried changing my ~/.ssh/config file to

Host *
 AddKeysToAgent yes
 UseKeychain yes
 IdentityFile /root/.ssh/id_rsa

but still no luck

from docker-lambda.

@pierrerappolt right, they're probably macOS-specific settings that don't work on Linux.

Might be best just to connect the files you need then instead of the whole .ssh directory

from docker-lambda.

@mhart Is there a way I can run npm install from within bash?

from docker-lambda.

I am able to create new working github permissions within bash but then can't run npm install

from docker-lambda.

Not sure what you mean? What happens when you run npm install?

from docker-lambda.

@mhart
after doing:
docker run -v "$HOME/.ssh":/root/.ssh -it lambci/lambda:build-nodejs4.3 bash

no such file or directory, open '/var/task/package.json'

from docker-lambda.

bash-4.2# npm install in between those

from docker-lambda.

Right – so the -v option to docker is used to expose your local directories on the docker container. So you'll need -v "$PWD":/var/task if you want to expose your (current) project directory

from docker-lambda.

@mhart Doh! Solved! Thank you so much!

from docker-lambda.

No probs, glad it worked for you 👍

from docker-lambda.