Skip to content

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

Closed
wxiaoguang opened this issue Jun 8, 2022 · 10 comments
Labels
topic/distribution This PR changes something about the packaging of Gitea type/bug

Comments

@wxiaoguang
Copy link
Contributor

Some docker users are affected by this bug (not only one) when they try to add public keys.

Can not verify your SSH key: SSHKeyGenParsePublicKey: fail to parse public key: exec(629f88e0-5:SSHKeyGenParsePublicKey) failed: exit status 255() stdout: stderr: No user exists for uid 997 - No user exists for uid 997

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.

@zeripath
Copy link
Contributor

zeripath commented Jun 8, 2022

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?

@wxiaoguang
Copy link
Contributor Author

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.

@kubo6472
Copy link

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.

@wxiaoguang
Copy link
Contributor Author

Could you provide your setup details? A reproducible example would help the debug.

@kubo6472
Copy link

Nevermind, it was my configuration mistake

@wxiaoguang
Copy link
Contributor Author

Could you share your experiences? It will help other users. Thank you.

@kubo6472
Copy link

It's very specific, but sure:
image
I clicked this button, it made that error happen. It was downloaded from here: https://github.com/parkervcp/eggs/tree/master/software/gitea and it runs on Pterodactyl Panel

@wxiaoguang
Copy link
Contributor Author

No more feedbacks

@wxiaoguang wxiaoguang closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
@MvBonin
Copy link

MvBonin commented Mar 23, 2023

I use pterodactyl too and with this set to false, the error is still there.

@wxiaoguang
Copy link
Contributor Author

Can you help to provide more clues? Or could you help to provide a minimal reproduce setup instruction?

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
@delvh delvh added topic/distribution This PR changes something about the packaging of Gitea and removed theme/docker labels Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/distribution This PR changes something about the packaging of Gitea type/bug
Projects
None yet
Development

No branches or pull requests

5 participants