Pixie doesn't work on Rancher Desktop #447
Assignees
Labels
area/datacollector
Issues related to Stirling (datacollector)
kind/compatibility
Compatibility related to either K8s, architecture, library versions
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
|
Turns out that the VM started by rancher-desktop does not have Kernel config file, that’s a list of config entries originally used in building the kernel. Pixie uses it to patch the packaged headers to make them as close to the actual kernel as possible. lima-vm/alpine-lima#113 |
|
The file is available in the boot image: $ rdctl shell head /media/sr0/boot/config-virt
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 5.15.40 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=100301
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=23700 |
|
Thanks @jandubois ! I still need to verify on mac. Since initial examination shows that |
I don't know why, but on the M1 it seems to be under lima-rancher-desktop:~# head /media/vda/boot/config-virt
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm64 5.15.40 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=100301
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=23700I'll create an issue on the alpine-lima repo to see if we can do something to make sure the boot CD is always mounted on |
|
@yzhao1012 Could you include instructions here on how you got Pixie installed on RD, especially once you have it working on macOS? Thank you! |
Re: |
|
We have added 2 kernel config paths used by rancher-desktop's CDRom-boot kernel image, under @jandubois' information. You should be able to test this after this week's Vizier release. |
|
@yzhao1012 I got this exact error (with rancher desktop and dockerd runtime) and I tried to build vizier and deploy it by following the development guide Output of `skaffold run -f skaffold/skaffold_vizier.yaml`Generating tags...
I am just trying to build and deploy vizier with a macbook. Using minikube to build and deploy was also not successful since minikube uses a separate docker runtime and mounting host file system to minikube vm was problematic in mac os. |
|
Related issue: lima-vm/lima#450 |
zasgar
added
priority/important-longterm
@yzhao1012 - I just tested this on my Intel Macbook and it now works for me (I was previously able to reproduce the issue). Given that you've confirmed that it also works on M1 Macbook and Linux, should we add |
Dockerd runtime wont work. The reason is that PEM needs to access the host kernel's system filesystem to compile BPF code. |
@htroisi Is this confirmed to work on Macbook M1/M2? I still get the same error on my Macbook Pro M2 using Pixie 0.8.2+Distribution.401c92c.20230530203620.1.jenkins and the instructions from Install guide for Community Cloud, which installed gcr.io/pixie-oss/pixie-prod/vizier/pem_image:0.14.0 in my RD cluster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Pixie doesn't work on Rancher Desktop.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect pixie to work
Screenshots
Logs
Please attach the logs by running the following command:
pixie_logs_20220531221823.zip
App information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: