Community maintained Docker config for the knot server

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?

0
by ionchy.ca 0 comments
expand 1 commit
Add authorized_keys_command.conf with correct git directory
sign up or login to add to the discussion
1
by ionchy.ca 0 comments
expand 2 commits
Add authorized_keys_command.conf with correct git directory
Add UID and GID arguments to Dockerfile
sign up or login to add to the discussion
2
by ionchy.ca 1 comment
expand 3 commits
Add authorized_keys_command.conf with correct git directory
Add UID and GID arguments to Dockerfile
typo

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...)

sign up or login to add to the discussion
3
by ionchy.ca 0 comments
expand 4 commits
Add authorized_keys_command.conf with correct git directory
Add UID and GID arguments to Dockerfile
typo
another typo
closed without merging
sign up or login to add to the discussion
Labels

None yet.

Participants 1
AT URI
at://did:plc:ypsrm6ue6o5xk5kvbdhwtppm/sh.tangled.repo.pull/3ly3ytvmoja22