Open kjwierenga opened 11 months ago
This issue was caused because there was no write permission on the /Users/kjw/Library/Application Support/Lens/binaries/kubectl/1.24.15
directory. I don't know why that happened (maybe that is the actual bug).
Fixed by chmod +w /Users/kjw/Library/Application Support/Lens/binaries/kubectl/1.24.15
.
same issue:
info: [CLUSTER]: refresh {"accessible":true,"disconnected":false,"id":"9e6bc24da882517db87224b43ecce772","name":"kubernetes-admin@cluster.local","online":true,"ready":true} debug: Set kubectl version 1.20.15 for cluster version v1.20.4 using version map error: Failed to get binary directory EACCES: permission denied, open '/Users/alexwang/Library/Application Support/Lens/binaries/kubectl/1.20.15/.bash_set_path' {"code":"EACCES","errno":-13,"path":"/Users/alexwang/Library/Application Support/Lens/binaries/kubectl/1.20.15/.bash_set_path","stack":"Error: EACCES: permission denied, open '/Users/alexwang/Library/Application Support/Lens/binaries/kubectl/1.20.15/.bash_set_path'","syscall":"open"} error: [SHELL-SESSION]: failed to open a local shell Failed to get directory containing kubectl: Error: EACCES: permission denied, open '/Users/alexwang/Library/Application Support/Lens/binaries/kubectl/1.20.15/.bash_set_path' {"stack":"Error: Failed to get directory containing kubectl: Error: EACCES: permission denied, open '/Users/alexwang/Library/Application Support/Lens/binaries/kubectl/1.20.15/.bash_set_path'\n at /Applications/Lens.app/Contents/Resources/app.asar/node_modules/@lensapp/core/static/build/library/main.js:35190:23"} info: [CLUSTER]: refresh {"accessible":true,"disconnected":false,"id":"9e6bc24da882517db87224b43ecce772","name":"kubernetes-admin@cluster.local","online":true,"ready":true}
Same here. Just delete all the folders in /Users/xxx/Library/Application Support/Lens/binaries/kubectl and let Lens download again
Same issue. Delete Lens/binaries directory don't help. Seems Lens creates dir with no permissions and have to change it manually.
This was off
Same issue on Windows 10. Just place the kubectl binary under AppData\Roaming\Lens\binaries\kubectl\bundled
and it connects.
The option mentioned by @m-asfari was already on for me. However, toggling it off and on again fixed the issue.
In Windows 10, you can install WSL using PowerShell with the command wsl --install. After completing the installation, you will need to restart your system, and then WSL should be ready for normal use.
Describe the bug The terminal in Lens (both local and pod specific) failed to start.
To Reproduce Steps to reproduce the behavior:
Expected behaviour The terminal opens either locally or in the pod.
Actual behaviour The terminal screen hangs and shows "Connecting..." and a flash message "If terminal shell is not ready please check your shell init files, if applicable.".
Screenshots
Environment (please complete the following information):
Lens Version: Lens: 2023.10.181418-latest, Extension API: 6.22.6, Electron: 25.8.3, Chrome: 114.0.5735.289, Node: 18.15.0, © 2023 Mirantis, Inc.
OS: macOS Ventura 13.5.2 (22G91)
Installation method (e.g. snap or AppImage in Linux): Download from https://k8slens.dev/desktop.html
Logs: Running the application executable (
/Applications/Lens.app/Contents/MacOS/Lens
) or runningopen Lens
from the command line shows the following logging.Kubeconfig: Issue not cause by malformed kubeconfig.
Additional context No additional context.