-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
minikube ssh doesn't recognize the end of transmission signal from standard input #1957
Comments
Can replicate even on minikube 0.23, as I cannot use
|
This is a result of moving over to using the "SSHRunner" which uses the native go ssh library rather than the libmachine ssh library I'll have to investigate exactly what was added in the libmachine ssh library to capture the signal. |
I ran into this today while trying to automate the upload of an audit-policy-yaml file to /etc/kubernetes/audit-policy.yaml (see #1609) Instead I've resorted to base64 encoding the file content and supplying it as a command line argument.
It would be good to have a way to upload files to minikube VM before it starts localkube. |
#2110 will help |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@zakame Try this:
|
Is this a BUG REPORT or FEATURE REQUEST? (choose one): bug
Environment:
Minikube version (use
minikube version
): 0.22.0 & 0.22.1cat ~/.minikube/machines/minikube/config.json | grep DriverName
): xhyvecat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): testingWhat happened:
I have a script that copies some files to minikube machine. In general it is something like this:
It worked with minikube 0.21.0. With 0.22.0 and 0.22.1 the ssh command waits for the end of input stream forever. It doesn't recognize that the file was already transmitted. The same happens with standard input.
What you expected to happen:
I expect that the minikube ssh process will exit after end of the transmission (Ctrl+D)
How to reproduce it (as minimally and precisely as possible):
Write couple of characters and type Ctrl+D. Nothing happens.
If you change version to 0.21.0 then after Ctrl+D command is finished.
The text was updated successfully, but these errors were encountered: