-
Notifications
You must be signed in to change notification settings - Fork 64
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
Failed to update dependencies #558
Comments
@alexwilson1 Thanks for raising this issue, I have noticed this issue after recent release. I will check on the permissions issue for kubectl binaries folder and update them in the upcoming release. |
Thanks! Although we've been seeing this issue for at least a month or more... does this still seem like an issue with recent release? Additionally, not sure why it is sporadic. |
@alexwilson1 it was introduced with release which had changes for mac arm64 support which is in Jan release. Previous to Jan releases this issue was not occurring. I will update once this is fixed. Thank you. |
I would need this feature too, would there be any plans to add support in the near future? |
Describe the bug
When attempting to use the extension, we occasionally receive the error:
Failed to update dependencies: Failed to move kubectl to bridge folder with error: Failed to retrieve kubectl version: Failed to execute: /home/vscode/.vscode-server/data/User/globalStorage/mindaro.mindaro/file-downloader-downloads/bridge/kubectl/linux/kubectl version --short --client -o json. Error: spawn /home/vscode/.vscode-server/data/User/globalStorage/mindaro.mindaro/file-downloader-downloads/bridge/kubectl/linux/kubectl EACCES
This is solved by running
chmod u+x /home/vscode/.vscode-server/data/User/globalStorage/mindaro.mindaro/file-downloader-downloads/bridge/kubectl/linux/kubectl
Mention the platform you are using
VSCode Devcontainers Linux arm64 6.5.0-15-generic
macOS Sonoma Version 14.3.1
mindaro 2.0.120240111
Happens with Docker Desktop and Colima.
To Reproduce
Unclear repro steps, happens occasionally. We think it might be related to closing a VSCode window where bridge is running before disconnecting the bridge.
Expected behavior
The error does not occur
Logs:
After searching the logs folder for 'EACCES', we find the term does not appear in the log files.
The text was updated successfully, but these errors were encountered: