Resolve host key generation issue #11
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Everytime the container goes up and down, the SSH host keys are regenerated and it gives a spooky error message. We need to make those persistent somehow. Needs to be investigated. We currently use the internal Gitea ssh server, so maybe it is just another configuration switch.
We could store host keys in
docker secret, maybe, which would solve the problem of securely persisting them across reboots -- you got any ideas how we easily mount a secret at a custom location (i.e. str8 into/etc/ssh/.., or edit the SSH config to get the host key from/run/secrets/..?That sounds good but I think the problem needs investigating first. There are some keys stored on the volume but I think they are from before the migration from Dokku and not used anymore. I think somehow Gitea is generating them again and not even saving them to the file system because we make use of the internally implemented SSH server (yep, that is right, golang programmers re-wrote SSH and it actually works!). I think it all stems from my botched migration basically. Would be cool to pair and sort this out one day.
Ok, I sank some time into this. It seems that the flow is this. We have a volume mounted for the gitea container living at
/var/lib/docker/volumes/gitea_git/_data. In there, there is asshfolder. Now, when Gitea turns on, it generates host keys into that folder. The first time, it sets thegogs.rsa.pubto1000:1000permissions. Things work. The next time Gitea turns on, it sems thegogs.rsa.pubfile toroot:rootpermissions and then complains that it can't access it and then generates an in-memory ssh host key which is different! Then we get the spooky error message. So, unable to find a real cause to this, I went ahead and just ranchattr +i gogs.rsaandchattr +i gogs.rsa.pubso that Gitea can't mistakenly reset the permissions for the host keys and they persist and are used. I don't even know if I should raise a bug about this or what is the root of it but it seems solved for now.