-
Notifications
You must be signed in to change notification settings - Fork 66
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
Is k3s on raspberry os supported (raspberry pi 4/8 GB)? #291
Comments
Is this repo abandoned? |
@zljubisic Thanks for your patience. It is not abandoned. I will look into the logs and get back here soon. Again Thanks. |
@zljubisic you are using arm 64 /aarch 64 OS, currently bridge supports it but the extension and build systems are not updated yet to make it work. There is workaround following instructions in this issue. Yes, bridge downloads its own version of kubectl to avoid conflicts or missing kubectl in dev's machine. Also I need your help to get the logs from Thanks for your patience, we will let you know once it is supported. |
@hsubramanianaks Thanks for the answer.
|
@zljubisic Thanks for your patience. This repo is dedicated for vscode extension for bridge, we track all issues in the main repo here. Of course, I agree, documentation updates for these kind of issues are missing. I will work with PM's to update them. Since for this issue we are already started working on updating the build systems , I have pinned it in the main repo here Also, I am planning to transfer this issue to main repo. Are you using docker for desktop Kubernetes cluster , because Bridge will not work with it. here is the documentation link for it. If not, I don't see reason why bridge would not work other than arm 64 images which we are already working. Can you share the logs from the location I specified in the previous comments please ? Thanks again. |
@hsubramanianaks Hi, logs are not in
Is that what you are looking for? |
@zljubisic these are vscode extension logs, you can share them as well. I am looking for CLI logs for example: in ubuntu via WSL2 it would be in location |
@hsubramanianaks As I explained in my very first post I am running VSCode on Windows 10 and than from it connect to host rpi4 on Raspbian OS. |
Type: Bug
I have an raspberry pi 4 (8 GB of ram) with raspberry pi os installed.
Using vscode on my windows computer i connected to the host rpi4 and installed bridge on kubernetes there. Now on rpi4, using vscode side bar's Kubernetes icon I can see k3s kubernetes cluster, its pods, services and so on.
As we know k3s installs its kubectl in /usr/local/bin/kubectl.
When I (ctrl+shift+P) execute "Bridge to kubernetes: Configure" I am asked to select the service, but nothing is offered to me. At the same time Kubernetes in vscode status line has triangle with exclamation inside of it.
Output of Bridge to kubernetes shows:
In this file, last few lines look like this:
I also saw in output of File Downloader this:
Why Bridge to kubernetes is downloading kubectl if there is one already installed?
For example, if I go to the folder: /home/pi/.vscode-server/data/User/globalStorage/mindaro.mindaro/file-downloader-downloads/bridge/kubectl/linux and exexcute:
why x86-64 architecture?
Does Bridge to kubernetes work in setup I have described?
Is there any workaround?
Extension version: 2.0.120230525
VS Code version: Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:57:04.379Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux arm64 5.15.84-v8+
The text was updated successfully, but these errors were encountered: