-
Notifications
You must be signed in to change notification settings - Fork 219
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
Cannot use ssh keys to push to github #620
Comments
Hi @Iolaum! I just tried to reproduce this and I kinda did but I'll need to double check with what you're getting. In my toolboxes when I type |
Hello @HarryMichal In my case I am the admin user of my installation. So typing In my case assume the following:
When I use toolbox I don't actually type
I also tested and I get the same result when I type Hope that helps. |
This is strange. It seems to me that you are trying to push to GitHub by authenticating with your public SSH key and for some reason it's refusing to let you in. What happens if you do:
GitHub doesn't offer shell access, so it would eventually error out anyway, but it should still say that you successfully authenticated. If I [ I think the |
I tried the
P.S. In the logs have substituted
From watching the logs I see that in the first attempt it finds the two ssh keys I have in my |
Thanks for the logs! I see that the entries with In the meantime, does setting |
I tested SSH_AUTH_SOCK and it fixed the issue!
Some additional information. My ssh folder does contain any of the default key names. There are two keys there with non standard names. Moreover since setting SSH_AUTH_SOCK fixed the issue I noticed that the first toolbox session
I m not sure if this is intended, however the lack of SSH_AUTH_SOCK in the second session looks to be the cause of this issue. P.S. Also note that this difference may be why |
Yes, I think the |
Closing. Thanks for stopping by, and helping debug this. Much appreciated. |
You 're welcome. Btw, I am not sure I understand. Will there be a PR to change the current behavior? Ie will there be changes to ensure that |
Describe the bug
In order to bypass #608 I create a user session after entering the container. However that session cannot push to github properly using ssh keys. If I exit that session I can then push, but I 'll have to re-enter it again to work on the code-base that requires the ability to change group ownership.
Steps how to reproduce the behaviour
Expected behaviour
Git push would succeed within a user session inside the container, just like it succeeds on initial session.
Actual behaviour
Git push fails due to access errors within the user session.
Screenshots
If applicable, add screenshots to help explain your problem.
Output of
toolbox --version
(v0.0.90+)Toolbox package info (
rpm -q toolbox
)Output of
podman version
Podman package info (
rpm -q podman
)Info about your OS
The text was updated successfully, but these errors were encountered: