avsm / docker-ssh-agent-forward Goto Github PK

I think usability could be greatly improved here.
Here's what I have in mind:

1. User has a wrapper script for her project, run.sh
2. User copies scripts from this project to her project.
3. User modifies run.sh script to have this:

cd ssh-agent-forward
. ./ssh-agent-forward.sh
cd ..
docker-compose up ...

4. User creates an ssh script ./docker/ssh_keys to be run inside a targeted docker container:

cat <<EOF >> ~/.ssh/config
Host *
User $SSH_USER
EOF

5. User modifies docker-compose.yml to have this:

environment:
  SSH_AUTH_SOCK: $SSH_AUTH_SOCK
  SSH_USER: $USER # can override in docker-compose.override.yml
command: sh -c "./docker/ssh_keys"

For this to work, SSH forward script should run the thing (skip if it's already done) and export SSH_AUTH_SOCK variable.

I see some unmerged PR's attempting to fix issues. Even with those PRs I was not able to make this work on my system. Also since this has not been updated since 2 years I searched for alternatives.

If you, like me, just search for a working solution, you can try https://github.com/abrugh/docker-ssh-agent-forward. It's a fork of this one and worked right out of the box for me.

I think this project could benefit from an illustration:

I hope it's a correct representation of what's going on here.

How would one use this with docker-compose? Thanks!

$ make

./pinata-build-sshd.sh: line 3: cd: /usr/local/share/pinata-ssh-agent: No such file or directory

The issue is that
./pinata-build-sshd.sh
hardcodes the PREFIX path to /usr/local instead of uses Env var PREFIX as done in the Makefile

I was wondering if you could tag v1 release so we can have a specific SHA for a stable release.
Many thanks.

Docker 1.12+ handles an init process now

Anyone knows this issue?

root # $ pinata-ssh-forward
[email protected]'s password:

Ever since upgrading to Sierra, this doesn't work for me anymore. Anyone else seeing this / have a workaround?