https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
doesn't look to be a RD thing, but you seem to be missing an ssh key used for authenticating to that repo inside the container.
f
how to bring the ssh key inside container
I didn't face this issue, in docker desktop
followed all the steps in Rancher desktop installation document
w
most folks will include it in their Dockerfile
f
we are running terraform code
w
its not a RD thing or really a DD thing. this is your authentication to git.ouryahoo.com
yeah but your module is hosted in git
i would talk to your git service admins if you are unsure on how to authenticate to the system
f
outside container I am able to clone
w
yes as i am guessing you have a sshkey in your .ssh directory
f
yes, I have
w
again better to talk about internal authentication and authorization with folks inside your org and not a random slack channel
f
already I reached them, everything fine.
this Rancher desktop having the issue
w
yes and everything is. you just are unfamiliar with how to include an sshkey in your container run
rancher desktop does not do anything for that so this channel will be of limited help
f
below is the command
Copy code
docker run -v ssh-agent:/ssh-agent -v ~/git:/git -v ~/.aws:/root/.aws -v ~/.ssh:/root/.ssh -e SSH_AUTH_SOCK=/ssh-agent/ssh-agent.sock -it --entrypoint=/bin/bash <http://docker.ouroath.com:4443/mscdi:latest|docker.ouroath.com:4443/mscdi:latest> -i
w
you are doing a bind mount so you can always do a 
rdctl shell
and see if you can clone manually
f
where i need to do, outside container?
w
yes that will give you a shell into the VM that runs the containers. or you can do a 
-it bash
to get a shell in the container you are trying to create. then manually test
none of us have any insight into that image as it looks to be proprietary to oath/yahoo so you will need to debug the env
the error is just saying it can't auth so that volume mount isn't doing what you think it is
you could also try fully qualifying the host side of your volume mount to be sure its pulling from where you think it is
lots of ~ in that docker run so maybe /Users/username/.ssh instead of ~/.ssh
2 Views
Open in Slack
PreviousNext
Powered by