Workaround for https://github.com/docker/for-mac/issues/483
100K+
Forward SSH agent socket into a container
Still experimental -- contact [email protected] or [email protected] if you want help.
Assuming you have a /usr/local
$ git clone git://github.com/uber-common/docker-ssh-agent-forward
$ cd docker-ssh-agent-forward
$ make
$ make install
On every boot, do:
pinata-ssh-forward
and the you can run pinata-ssh-mount to get a Docker CLI fragment that adds
the SSH agent socket and sets SSH_AUTH_SOCK within the container.
$ pinata-ssh-mount
-v ssh-agent:/ssh-agent -e SSH_AUTH_SOCK=/ssh-agent/ssh-agent.sock
$ docker run -it $(pinata-ssh-mount)
/ssh-agent-forward ssh -T [email protected]
The authenticity of host 'github.com (192.30.252.128)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,192.30.252.128' (RSA) to the list of known hosts.
PTY allocation request failed on channel 0
Hi avsm! You've successfully authenticated, but GitHub does not provide shell access.
To fetch the latest image, do:
pinata-ssh-pull
To build an image yourself rather than fetching from Docker Hub, run
./pinata-ssh-build.sh from your clone of this repo.
We didn't bother installing the build script with the Makefile since using the hub image should be the common case.
License is ISC.
Content type
Image
Digest
Size
4.4 MB
Last updated
almost 9 years ago
docker pull uber/ssh-agent-forward