-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Podman latest version 5.0.3 affected our entire development team #22965
Comments
Please provide the info requested in the issue template. From the shown error message it sounds like something in your environment is killing the ssh-keygen command. |
I'm really sorry i just posted this question in hurry reason more than 20 users affected with latest version, we are using widows machine and we are connected to VPN network, so far we have used 4.9.3 its workes perfectly. now after updating the version version we can see this issue across our machhine. |
it would be really helpful you can help me out about this issue because we have installed Podman across our organization when user will upgrade the podman all the folks will getting into trouble. |
@tppalani Could you check if there are any private/public keys in the |
You could also consider a |
Thanks for help. I'm using podman version 4.9.4 inside my local path in windows system, i don't see any keys in it, but my pod is up and running past 1 year %USERPROFILE%/.local/share/containers/podman/machine/ directory (usually named machine and machine.pub)? My question is - why this ssh key issue coming in latest version how to fix this if key not exist, if already exist it will start podman automatically ? |
Ho @BlackHole1 do you have any updates on this? |
Hi @tppalani. I reviewed the relevant code, but the code responsible for generating ssh has not been updated for 2 years (see: https://github.com/containers/podman/blame/26370c95b79e82f5f0cac0c61eeb55021e7b0f77/pkg/machine/keys.go#L71-L90). You can try manually executing the command: |
Thanks again. just one doubt in above command will create new private, public key inside the this directory path %USERPROFILE%/.local/share/containers/podman/machine? |
No, you need to navigate to this directory in the terminal first and then execute this command. |
PS C:\Users\User.local\share\containers\podman\machine> ssh-keygen -N "" -t ed25519 -f machine |
The output returned seems to be a quirk of Microsoft PowerShell. Try and run the command and also include the PS stop parsing operator before the others
|
Hi @thimslugga you mean if I run this command from PowerShell this will create new private and public key? ssh-keygen.exe --% -t dsa -N "" -f stuff |
Yah I would give that a try as it looked like you were using PS from your shared output. I'm not a Windows user myself. |
A friendly reminder that this issue had no activity for 30 days. |
Issue Description
We have installed podman latest version 5.0.3 into our machine all the machine are getting failed with below error. Error key generation failed, unable to read from stderr signal killed
![latest-podman](https://private-user-images.githubusercontent.com/6921037/338633552-c40bce76-095d-442f-823c-cfa8221b6d63.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjEzOTczNzUsIm5iZiI6MTcyMTM5NzA3NSwicGF0aCI6Ii82OTIxMDM3LzMzODYzMzU1Mi1jNDBiY2U3Ni0wOTVkLTQ0MmYtODIzYy1jZmE4MjIxYjZkNjMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTlUMTM1MTE1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NzcyOTlkNTViYTBkZjVhNGY4OGVkNzFkOWE0OTE5OGNlNjdmYWJlMDM1ZmU0MWEzYjQ0YTFjZjY0NmIwZTE4YiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.S8j8b7QqodfQHnDfvGgVjGuoGrthRoQs5O4mG7Raaqg)
Steps to reproduce the issue
Describe the results you received
Attched image
Describe the results you expected
Describe the results you expected
podman info output
If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: