-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docker ssh passthrough docs #13732
Conversation
Codecov Report
@@ Coverage Diff @@
## master #13732 +/- ##
=======================================
Coverage 42.15% 42.15%
=======================================
Files 708 708
Lines 77123 77123
=======================================
+ Hits 32510 32515 +5
+ Misses 39269 39265 -4
+ Partials 5344 5343 -1
Continue to review full report at Codecov.
|
``` | ||
ln -s /var/lib/gitea/git/.ssh/authorized_keys /home/git/.ssh/authorized_keys | ||
```bash | ||
ssh -p 2222 -o StrictHostKeyChecking=no [git@127.0.0.1](mailto:git@127.0.0.1) "SSH_ORIGINAL_COMMAND=\"$SSH_ORIGINAL_COMMAND\" $0 $@" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this mailto may have snuck in unintentionally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to remove it - I just used what Gitea already uses in this place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed it.
Thanks for this PR, @pat-s, it helped me get ssh passthrough working :) |
As discussed in Discord with @zeripath, a major rewrite and simplification of the docker SSH passthrough docs.
Changelog summary
.ssh/authorized_keys
→ confusing and unstable due toSSH_AUTHORIZED_KEYS_BACKUP
optionRelated issues
I am not sure if PR #12626 is valid or not - for me it worked with the current setup on the latest dev version. But this is not necessarliy important for this PR.