Skip to Content
Last modified by Alexandru Pentilescu on 2024/07/16 22:44
From version 13.1
edited by Alexandru Pentilescu
on 2024/07/16 21:59
Change comment: There is no comment for this version
To version 14.1
edited by Alexandru Pentilescu
on 2024/07/16 22:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -199,3 +199,28 @@
199 199  
200 200  Copy its contents and add it to your Gitea's user settings through the web interface, as follows:
201 201  [[image:1.png]][[image:2.png]][[image:3.png]]
202 +
203 +Once the public key is registered here, you should be able to do git push and git pull from this particular repository using SSH, without the need for further authentication. However, there's still a couple more steps left to follow:
204 +
205 +== Generate a public/private keypair for the git user as well ==
206 +
207 +This might not be immediately obvious why this is necessary, but in order for the SSH passthrough to work, the git user that we'll log into in the future will have to forward all SSH requests to inside the docker container. In order to do so, the container's own SSH server will need to recognize the requests as authenticated from the git user on the host machine.
208 +
209 +To this end, we will have to generate a keypair for the git user as well:
210 +
211 +{{code language="bash"}}
212 +sudo -u git ssh-keygen -t rsa -b 4096 -C "Gitea Host Key"
213 +{{/code}}
214 +
215 +Once this part is done register the newly generated public key to the SSH server inside the docker container, by appending it to the /home/git/.ssh/authorized_keys files inside the host.
216 +
217 +To do so, please do:
218 +
219 +{{code language="bash"}}
220 +sudo -u git cat /home/git/.ssh/id_rsa.pub | sudo -u git tee -a /home/git/.ssh/authorized_keys
221 +sudo -u git chmod 600 /home/git/.ssh/authorized_keys
222 +{{/code}}
223 +
224 +You might wonder why we're changing a file on the host filesystem and not inside the docker, where the relevant SSH service is running. The reason for this is, remember, this particular directory is already mapped in our docker-compose.yml file, so it exists in both the host machine and in the docker container, simultaneously. All changes that take place to it on the host will reflect inside the container.
225 +
226 +