-
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
improve minikube cp error message #17576
Comments
Running the command directly in the cluster container provides the expected error message:
|
Calling |
/assign |
/assign I want to give it a try as first contribution please :) |
I honestly dislike, that the PR #17715 was committed just 1 hour after I have claimed this issue. |
I am sorry, I am new here as well. I've seen this ticket got unassigned and I tried to follow the process, but wrongly 😞.
I forgot to mention in a comment, that I plan to work on it. When I opened the PR and tried to assign it to me, I realized it was already assigned to you in the meantime while I was working on the ticket. Again, I am sorry, for the chaos, I've created. If you have the solution ready and you would like to create PR yourself, I can close mine. |
Hi @martinjirku |
What Happened?
When trying to
minikube cp
a file, I got the following error:After checking the logs, it appeared to be caused by a permission error:
So I spent a couple hours testing permission changes.
However, I am naive and glossed over the preceding message...
existence check
....Is there any way to improve the message in stderr here?
Or can we add an option to
minikube cp
for automatically creating directories that don't yet exist?Thank you for your time.
Attach the log file
Operating System
None
Driver
None
The text was updated successfully, but these errors were encountered: