blocks|key|49074|text|默认情况下，boot2docker仅共享/Users下的文件。SSH_AUTH_SOCK可能在/tmp下，所以-v挂载的是虚拟机的代理，而不是来自您的mac的代理。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|49075|如果您将VirtualBox设置为共享/tmp，它应该可以正常工作。|49076|entityMap^0|K|6|V|D|1B|4|1J|2|0|J|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

By default, boot2docker shares only files under <code>/Users</code>. <code>SSH_AUTH_SOCK</code> is probably under <code>/tmp</code> so the <code>-v</code> mounts the agent of the VM, not the one from your mac.

If you setup your VirtualBox to share <code>/tmp</code>, it should be working.

blocks|key|49093|text|我遇到了类似的问题，通过在主模式下使用带有控制套接字的ssh，并将其全部封装在一个脚本中，可以使事情变得非常无缝：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49094|#!/bin/sh+++

ssh+-i+~/.vagrant.d/insecure_private_key+-p+2222+-A+-M+-S+ssh.socket+-f+docker@127.0.0.1+tail+-f+/dev/null

HOST_SSH_AUTH_SOCK=$(ssh+-S+ssh.socket+docker@127.0.0.1+env+%7C+grep+"SSH_AUTH_SOCK"+%7C+cut+-f+2+-d+=)

docker+run+-v+$HOST_SSH_AUTH_SOCK:/ssh-agent+\
+++++++-e+"SSH_AUTH_SOCK=/ssh-agent"+\
+++++++-t+hello-world+"$@"

ssh+-S+ssh.socket+-O+exit+docker@127.0.0.1|code-block|syntax|javascript|49095|这不是世界上最漂亮的事情，但比手动保持SSH会话打开要好得多。|49096|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I ran into a similar issue, and was able to make things pretty seamless by using ssh in master mode with a control socket and wrapping it all in a script like this:

<pre><code>#!/bin/sh 

ssh -i ~/.vagrant.d/insecure_private_key -p 2222 -A -M -S ssh.socket -f docker@127.0.0.1 tail -f /dev/null

HOST_SSH_AUTH_SOCK=$(ssh -S ssh.socket docker@127.0.0.1 env | grep "SSH_AUTH_SOCK" | cut -f 2 -d =)

docker run -v $HOST_SSH_AUTH_SOCK:/ssh-agent \
 -e "SSH_AUTH_SOCK=/ssh-agent" \
 -t hello-world "$@"

ssh -S ssh.socket -O exit docker@127.0.0.1
</code></pre>

Not the prettiest thing in the universe, but much better than manually keeping an SSH session open IMO.

blocks|key|49147|text|我对@wilwilson的回答进行了扩展，并创建了一个在OSX+boot2docker环境中设置代理转发的脚本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|49148|https://gist.github.com/rcoup/53e8dee9f5ea27a51855|offset|length|49149|#!/bin/bash

#+Use+a+unique+ssh+socket+name+per-invocation+of+this+script
SSH_SOCK=boot2docker.$$.ssh.socket

#+ssh+into+boot2docker+with+agent+forwarding
ssh+-i+~/.ssh/id_boot2docker+\
++++-o+StrictHostKeyChecking=no+\
++++-o+IdentitiesOnly=yes+\
++++-o+UserKnownHostsFile=/dev/null+\
++++-o+LogLevel=quiet+\
++++-p+2022+docker@localhost+\
++++-A+-M+-S+$SSH_SOCK+-f+-n+\
++++tail+-f+/dev/null

#+get+the+agent+socket+path+from+the+boot2docker+vm
B2D_AGENT_SOCK=$(ssh+-S+$SSH_SOCK+docker@localhost+echo+\$SSH_AUTH_SOCK)

#+mount+the+socket+(from+the+boot2docker+vm)+onto+the+docker+container
#+and+set+the+ssh+agent+environment+variable+so+ssh+tools+pick+it+up
docker+run+\
++++-v+$B2D_AGENT_SOCK:/ssh-agent+\
++++-e+"SSH_AUTH_SOCK=/ssh-agent"+\
++++"$@"

#+we're+done;+kill+off+the+boot2docker+ssh+agent
ssh+-S+$SSH_SOCK+-O+exit+docker@localhost|code-block|syntax|javascript|49150|将其放入~/bin/docker-run-ssh，使用chmod+%2Bx，并使用docker-run-ssh而不是docker+run。|style|CODE|49151|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1E|0|0|0|4|K|R|8|13|E|1K|A|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|H|7|10|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|11|8|@$D|12|E|13|M|N]|$D|14|E|15|M|N]|$D|16|E|17|M|N]|$D|18|E|19|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]]]

I expanded on @wilwilson's answer, and created a script that will setup agent forwarding in an OSX boot2docker environment.

<a href="https://gist.github.com/rcoup/53e8dee9f5ea27a51855" rel="nofollow">https://gist.github.com/rcoup/53e8dee9f5ea27a51855</a>

<pre><code>#!/bin/bash

# Use a unique ssh socket name per-invocation of this script
SSH_SOCK=boot2docker.$$.ssh.socket

# ssh into boot2docker with agent forwarding
ssh -i ~/.ssh/id_boot2docker \
 -o StrictHostKeyChecking=no \
 -o IdentitiesOnly=yes \
 -o UserKnownHostsFile=/dev/null \
 -o LogLevel=quiet \
 -p 2022 docker@localhost \
 -A -M -S $SSH_SOCK -f -n \
 tail -f /dev/null

# get the agent socket path from the boot2docker vm
B2D_AGENT_SOCK=$(ssh -S $SSH_SOCK docker@localhost echo \$SSH_AUTH_SOCK)

# mount the socket (from the boot2docker vm) onto the docker container
# and set the ssh agent environment variable so ssh tools pick it up
docker run \
 -v $B2D_AGENT_SOCK:/ssh-agent \
 -e "SSH_AUTH_SOCK=/ssh-agent" \
 "$@"

# we're done; kill off the boot2docker ssh agent
ssh -S $SSH_SOCK -O exit docker@localhost
</code></pre>

Stick it in <code>~/bin/docker-run-ssh</code>, <code>chmod +x</code> it, and use <code>docker-run-ssh</code> instead of <code>docker run</code>.

blocks|key|4555642|text|一句话：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4555643|下面是如何在运行Debian+Jessie镜像的Ubuntu+16上设置它：|4555644|docker+run+--rm+-it+--name+container_name+\
-v+$(dirname+$SSH_AUTH_SOCK):$(dirname+$SSH_AUTH_SOCK)+\
-e+SSH_AUTH_SOCK=$SSH_AUTH_SOCK+my_image|code-block|syntax|javascript|4555645|https://techtip.tech.blog/2016/12/04/using-ssh-agent-forwarding-with-a-docker-container/|offset|length|4555646|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|2G|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|W|8|@]|9|@$K|X|L|Y|1|Z]]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|J]]]]

A one-liner: 

Here’s how to set it up on Ubuntu 16 running a Debian Jessie image:

<pre><code>docker run --rm -it --name container_name \
-v $(dirname $SSH_AUTH_SOCK):$(dirname $SSH_AUTH_SOCK) \
-e SSH_AUTH_SOCK=$SSH_AUTH_SOCK my_image
</code></pre>

<a href="https://techtip.tech.blog/2016/12/04/using-ssh-agent-forwarding-with-a-docker-container/" rel="noreferrer">https://techtip.tech.blog/2016/12/04/using-ssh-agent-forwarding-with-a-docker-container/</a>

blocks|key|4555668|text|从2.2.0.0版本开始，docker+for+macOS允许用户在容器内访问主机的SSH代理。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4555669|下面是一个命令示例，让您执行此操作：|4555670|docker+run+--rm+-it+\
-v+/run/host-services/ssh-auth.sock:/ssh-agent+\
-e+SSH_AUTH_SOCK="/ssh-agent"+\
my_image|code-block|syntax|javascript|4555671|请注意，您必须挂载特定的路径(/run/host-services/ssh-auth.sock)，而不是$SSH_AUTH_SOCK环境变量中包含的路径，就像在linux主机上所做的那样。|4555672|entityMap^0|1|7|0|0|0|F|W|1G|E|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

Since version <code>2.2.0.0</code>, docker for macOS allows users to access the host’s SSH agent inside containers.

Here's an example command that let's you do it:

<pre><code>docker run --rm -it \
-v /run/host-services/ssh-auth.sock:/ssh-agent \
-e SSH_AUTH_SOCK="/ssh-agent" \
my_image
</code></pre>

Note that you have to mount the specific path (<code>/run/host-services/ssh-auth.sock</code>) instead of the path contained in <code>$SSH_AUTH_SOCK</code> environment variable, like you would do on linux hosts.

I would like to use ssh-agent to forward my keys into the docker image and pull from a private github repo.

I am using a slightly modified version of <a href="https://github.com/phusion/passenger-docker">https://github.com/phusion/passenger-docker</a> with boot2docker on Yosemite.

<pre><code>ssh-add -l
...key details
boot2docker up
</code></pre>

Then I use the command which I have seen in a number of places (i.e. <a href="https://gist.github.com/d11wtq/8699521">https://gist.github.com/d11wtq/8699521</a>):

<pre><code>docker run --rm -t -i -v $SSH_AUTH_SOCK:/ssh-agent -e SSH_AUTH_SOCK=/ssh-agent my_image /bin/bash
</code></pre>

However it doesn't seem to work:

<pre><code>root@299212f6fee3:/# ssh-add -l
Could not open a connection to your authentication agent.

root@299212f6fee3:/# eval `ssh-agent -s`
Agent pid 19

root@299212f6fee3:/# ssh-add -l
The agent has no identities.

root@299212f6fee3:/# ssh git@github.com
Warning: Permanently added the RSA host key for IP address '192.30.252.128' to the list of known hosts.
Permission denied (publickey).
</code></pre>

Using ssh-agent with docker on macOS

虚拟机

容器

Docker

Ubuntu

Debian

我想使用ssh-agent将我的密钥转发到docker镜像中，并从私有github存储库中提取。我在Yosemite上使用的是略微修改过的和boot2docker版本。ssh-add -l...key detailsboot2docker up然后，我使用我在许多地方看到的命令(即)：docker run --rm -...

问在macOS上使用带有docker的ssh代理
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在macOS上使用带有docker的ssh代理EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在macOS上使用带有docker的ssh代理
EN