-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Can not verify your SSH key: SSHKeyGenParsePublicKey failed: exit status 255 No user exists for uid 997 #19920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
As far as I can see our entrypoint (for the docker with root) would ensure that the USER_UID is in the /etc/passwd file. Therefore I think this can only happen on the root docker if they're not using our entrypoint - I don't think we can be expected to correctly configure things if they're not using our entrypoint. On the rootless - do we really use ssh-keygen there? |
I have checked the entrypoint logic and tried to play a while, but I have difficulty to reproduce the problem (I do not know what the users have done on their side .....) Another thing that I do not understand is whose UID is 997. In most Linux distro, the 997 doesn't seem to be a common UID, and it doesn't seem to be easily used by a user by mistake. |
988 for me. Experiencing basically the same thing. |
Could you provide your setup details? A reproducible example would help the debug. |
Nevermind, it was my configuration mistake |
Could you share your experiences? It will help other users. Thank you. |
It's very specific, but sure: |
No more feedbacks |
I use pterodactyl too and with this set to false, the error is still there. |
Can you help to provide more clues? Or could you help to provide a minimal reproduce setup instruction? |
Some docker users are affected by this bug (not only one) when they try to add public keys.
It's likely cased by the error reported by the
ssh-keygen
command executed by Gitea, which meets the non-existing UID 997.I don't know how it happens at the moment. For Gitea Docker, the UID should have been default to 1000, maybe user's setup steps/configs/operations could provide some clues.
The text was updated successfully, but these errors were encountered: