Open ismaeIfm opened 2 years ago
yzhao1012
commented
2 years ago 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.
https://github.com/lima-vm/alpine-lima/issues/113 I have created this issue on lima-vm, which is the VM tool used by rancher-desktop.
jandubois
commented
2 years ago 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=23700Thanks @jandubois !
I've added /media/sr0/boot/config-virt into Pixie's config search path, and verified that Pixie now works fine on rancher-desktop, on Ubuntu Linux.
I still need to verify on mac. Since initial examination shows that /media/sr0/boot/config-virt does not exist on my m1 macbook air running with Lima VM.
jandubois
commented
2 years ago I still need to verify on mac. Since initial examination shows that
/media/sr0/boot/config-virtdoes not exist on my m1 macbook air running with Lima VM.
I don't know why, but on the M1 it seems to be under vda:
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 /media/cdrom to have a predictable location; I don't know why this isn't the case right now.
jandubois
commented
2 years ago @yzhao1012 Could you include instructions here on how you got Pixie installed on RD, especially once you have it working on macOS? Thank you!
yzhao1012
commented
2 years ago @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: Once rancher-desktop is installed and launched, follow https://docs.px.dev/installing-pixie/install-guides/community-cloud-for-pixie to install Pixie. That instruction just uses local kubectl config to figure out the target kubernetes cluster and how to reach it. Then deploy Pixie with a predefined packages from public GCR repos.
yzhao1012
commented
2 years ago We have added 2 kernel config paths used by rancher-desktop's CDRom-boot kernel image, under @jandubois' information. See https://github.com/pixie-io/pixie/commit/57e1dfd2f335d59521ec35c2191ca84c4d12e89d
You should be able to test this after this week's Vizier release.
tharinduwijewardane
commented
2 years ago @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 (Pls note I have to manually set the DOCKER_ID and GROUP_ID in latest run_docker.sh script.) But I keep getting the following output.
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.
zasgar
commented
2 years ago Related issue: lima-vm/lima#450
htroisi
commented
2 years ago You should be able to test this after this week's Vizier release.
@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 Rancher Desktop as a supported environment to Pixie's Requirements page?
yzhao1012
commented
2 years ago Related issue: lima-vm/lima#450
with rancher desktop and dockerd runtime
Dockerd runtime wont work. Actually, you have to use the VM driver, like what Hannah and I tested with rancher-desktop. As docker (or any container-based kubernetes desktop environment) is not compatible with Pixie (PEM specifically).
The reason is that PEM needs to access the host kernel's system filesystem to compile BPF code. Container-based kubernetes desktop environment hides the host filesystem from PEM and breaks it.
rainan16
commented
1 year ago @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
Rancher Desktopas a supported environment to Pixie's Requirements page?
@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/pemimage:0.14.0 in my RD cluster.
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.