All of lore.kernel.org
 help / color / mirror / Atom feed
From: "embedded (VIVAVIS AG)" <embedded@vivavis.com>
To: Sourabh Hegde <hrsourabh011@gmail.com>,
	Nicolas Jeker <n.jeker@delisys.ch>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: AW: [yocto] Fetch private gitlab repo using ssh with Yocto recipe #bitbake
Date: Fri, 28 Jan 2022 10:27:30 +0000	[thread overview]
Message-ID: <79aff859cb334b3f83a8c5c16cea7bc8@vivavis.com> (raw)
In-Reply-To: <CADYjeSsxC=LzFMLGTZy1u4m_MfNsHJ3Nq3Y+zYwY_toJYZFhMg@mail.gmail.com>

Hi,
 
> Von: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> Im Auftrag von Sourabh Hegde
> Gesendet: Freitag, 28. Januar 2022 10:47
>
> Can you please let me know how to "forward SSH_AGENT into it to be able
> to fetch from internal projects without the need to mount the key into the container."? I never did that before.

I use the following options within the Docker run command:
  -v $SSH_AUTH_SOCK:/ssh.socket \
  -e SSH_AUTH_SOCK=/ssh.socket \

Furthermore, I had to mount the .ssh folder into the container to make it working (be aware of security risk).
Additionally, you should check that uid, gid of the user in the container is the same on the host.

Regards,

Carsten

  reply	other threads:[~2022-01-28 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  7:16 Fetch private gitlab repo using ssh with Yocto recipe #bitbake hrsourabh011
     [not found] ` <664d7ef6f28584b0d7310774ad48660437562589.camel@delisys.ch>
2022-01-28  9:46   ` [yocto] " Sourabh Hegde
2022-01-28 10:27     ` embedded (VIVAVIS AG) [this message]
     [not found]       ` <90997c2cb92ea9700451b0e5d9afaeef64f4662c.camel@delisys.ch>
2022-01-28 12:33         ` Erik Botö
2022-01-28 17:37       ` Khem Raj
2022-01-31 10:54         ` Sourabh Hegde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79aff859cb334b3f83a8c5c16cea7bc8@vivavis.com \
    --to=embedded@vivavis.com \
    --cc=hrsourabh011@gmail.com \
    --cc=n.jeker@delisys.ch \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.