updated docs with caveat for authorized_keys #13030
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Gitea makes authorized_keys backups by default. People following along with the "Installing with Docker" > "SSH Container Passthrough" section are asked to symlink their authorized_keys folder with a volume that is mounted inside the container, as described here: https://docs.gitea.io/en-us/install-with-docker/#ssh-container-passthrough. However, this symlink can end up pointing to a backup, leading to ssh not working as described in #12625.
Solution
Add the recommendation given by the author of #12625 as a second option to the docs and tell users to turn off authorized_keys backup if they want to go with the first option.