pixie icon indicating copy to clipboard operation
pixie copied to clipboard

Failed to execute script error on K3s cluster

Open juanitomint opened this issue 4 years ago • 6 comments

Describe the bug Hi there I'm playing around with Pixie and a k3scluster k3s [master] $ px run px/namespace -- --namespace pixie Pixie CLI Failed to execute script error=Script compilation failed: L152 : C22 Table 'http_events' not found.

To Reproduce Steps to reproduce the behavior:

  1. use https://github.com/juanitomint/k3s-cluster to spin up a local k3s cluster

  2. Installed pixie with helm $ helm install pixie pixie/pixie-chart --set deployKey=XXXX-xxxXXXXx-xXXXxxxx NAME: pixie LAST DEPLOYED: Mon May 24 12:32:36 2021 NAMESPACE: pixie STATUS: deployed REVISION: 1 TEST SUITE: None Install went without problems

  3. the cluster appears on https://work.withpixie.ai/

  4. tried to run k3s [master] $ px run px/namespace -- --namespace pixie

  5. See error Pixie CLI Failed to execute script error=Script compilation failed: L152 : C22 Table 'http_events' not found. Expected behavior see the details of a namespace

Screenshots If applicable, add screenshots to help explain your problem. Please make sure the screenshot does not contain any sensitive information such as API keys or access tokens.

Logs I can send you the pixie_logs_20210524124430.zip over slack just PM me at juan.borda

App information (please complete the following information):

  • Pixie version Pixie CLI 0.5.9+Distribution.c49ec7f.20210513154434.1
  • K8s cluster version: kubectl version Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1+k3s1", GitCommit:"75dba57f9b1de3ec0403b148c52c348e1dee2a5e", GitTreeState:"clean", BuildDate:"2021-05-21T16:12:29Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

Additional context will try using px deploy

juanitomint avatar May 24 '21 15:05 juanitomint

@juanitomint and I exchanged messages earlier over slack. Summary is that Pixie is not currently supported in environments where the host nodes are containers. The problem is that the container environment is not set-up for BPF.

oazizi000 avatar May 26 '21 03:05 oazizi000

Hey @oazizi000, could you please elaborate on the technical details? I am planning to play around with Pixie soon, and I'd like to use k3d as an environment, if possible. Could it be related to mounting the virtual /sys/fs/bpf kernel filesystem?

fktkrt avatar Sep 29 '21 08:09 fktkrt

@oazizi000 I just recently came across this as well . My nodes are setup as proxmox vms on k3s , would they be affected by the issue with containers you mentioned above?

SorsOps avatar Aug 01 '23 20:08 SorsOps

@SorsOps unfortunately they would be affected since k3s runs inside of a container.

ddelnano avatar Aug 02 '23 14:08 ddelnano

I think https://docs.px.dev/installing-pixie/requirements#kubernetes-local-development-environments needs to be updated to explicitly say that k3s is not supported as it gives conflicting info

SorsOps avatar Aug 02 '23 16:08 SorsOps

Sorry I may have misspoke with my previous comment. I haven't used k3s before and my earlier comment was based on my independent research. I trust our documentation more than my brief research, but let me confirm that.

@SorsOps for your k3s VMs are you able to confirm if k3s's components are running outside of a container?

ddelnano avatar Aug 02 '23 16:08 ddelnano