tangled.org / knot-docker
Community maintained Docker config for the knot server
fork atom

Add authorized_keys_command.conf to Dockerfile #4

closed opened by ionchy.ca targeting main from ionchy.ca/knot-docker: main

I couldn't push or pull from any repositories until I set -git-dir following the instructions in knot-hosting, so maybe this file should just created when creating the Dockerfile?

Labels

None yet.

Participants 1
AT URI
at://did:plc:ypsrm6ue6o5xk5kvbdhwtppm/sh.tangled.repo.pull/3ly3ytvmoja22
+3
Diff #0
unified split
+3
rootfs/etc/ssh/sshd_config.d/authorized_keys_command.conf
··· 1 + Match User git 2 + AuthorizedKeysCommand /usr/bin/knot keys -o authorized-keys -git-dir /home/git/repositories 3 + AuthorizedKeysCommandUser nobody

Submissions
sign up or login to add to the discussion
ionchy.ca submitted #3
diff interdiff
4 commits
expand
350aad4a
Add authorized_keys_command.conf with correct git directory
ebb28c22
Add UID and GID arguments to Dockerfile
e58c057c
typo
beb70707
another typo
closed without merging
ionchy.ca submitted #2
diff interdiff
3 commits
expand
350aad4a
Add authorized_keys_command.conf with correct git directory
ebb28c22
Add UID and GID arguments to Dockerfile
e58c057c
typo
ionchy.ca

I also added UID and GID args that can be set during build, so following the example command should fix #2 by providing a UID and GID that exist on the host so that the directories owned by git in the container can be bind mounted on the host. (I'm not sure how to change the title of the PR to reflect this...)

ionchy.ca submitted #1
diff interdiff
2 commits
expand
350aad4a
Add authorized_keys_command.conf with correct git directory
ebb28c22
Add UID and GID arguments to Dockerfile
ionchy.ca submitted #0
1 commit
expand
350aad4a
Add authorized_keys_command.conf with correct git directory