Skip to content
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

kubeshark CLI installation failed (CAP_CHECKPOINT_RESTORE kernel version incompatibility) #1470

Open
chrinly opened this issue Dec 21, 2023 · 9 comments

Comments

@chrinly
Copy link

chrinly commented Dec 21, 2023

docker version : 19.03.9
kubernetes version : 1.18.6

I use the CLI to install,This is the worker build error log

Error: Error response from daemon: invalid CapAdd: unknown capability: "CAP_CHECKPOINT_RESTORE"

Hopefully it will be resolved,This will help me tremendously

@lplazas
Copy link

lplazas commented Dec 22, 2023

What OS are you trying to install the CLI on?

@RafPe
Copy link

RafPe commented Dec 22, 2023

I can confirm that I experience the same on EKS. Node versions on 1.18

@alongir alongir changed the title kubeshark CLI installation failed kubeshark CLI installation failed (CAP_CHECKPOINT_RESTORE kernel version incompatibility) Dec 22, 2023
@alongir
Copy link
Member

alongir commented Dec 22, 2023

It appears this can cause a problem with certain kernel versions. We don't have the full details yet, but we'll probably fix it in the next few days.

@chrinly
Copy link
Author

chrinly commented Dec 25, 2023

What OS are you trying to install the CLI on?

I installed in centos 73.9
kernel version is 3.1

@chrinly
Copy link
Author

chrinly commented Dec 25, 2023

It appears this can cause a problem with certain kernel versions. We don't have the full details yet, but we'll probably fix it in the next few days.

Thank you very much for your reply. I hope the new version can solve my problem

@alongir
Copy link
Member

alongir commented Dec 25, 2023

For now, do this: --set tap.serviceMesh=false --set tap.tls=false

@taylorsmithgg
Copy link

taylorsmithgg commented Jan 4, 2024

Also experiencing Error: Error response from daemon: invalid CapAdd: unknown capability: "CAP_CHECKPOINT_RESTORE"

For now, do this: --set tap.serviceMesh=false --set tap.tls=false

These flags result in a CrashLoopBackOff in EKS v1.23.17

2024-01-04T18:13:39Z INF source/packet_source_manager.go:167 > Too many pods for setting ebpf filter 388, setting just not 443
2024-01-04T18:13:39Z INF source/packet_source_manager.go:173 > Setting pcap bpf filter port not 443

@RafPe
Copy link

RafPe commented Jan 8, 2024

So today I got kubeshark running - without making any other modifications into my platform setup.

❯ kubectl version
Client Version: v1.28.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.21.14-eks-8cb36c9
❯ k get nodes
NAME                                         STATUS   ROLES    AGE      VERSION
ip-*****.compute.internal    Ready    <none>   2y302d   v1.18.9-eks-d1db3c
ip-*****.compute.internal    Ready    <none>   2y205d   v1.18.9-eks-d1db3c
ip-*****.compute.internal    Ready    <none>   566d     v1.18.9-eks-d1db3c
ip-*****.compute.internal   Ready    <none>   2y302d   v1.18.9-eks-d1db3c
ip-*****.compute.internal   Ready    <none>   2y205d   v1.18.9-eks-d1db3c
ip-*****.compute.internal    Ready    <none>   2y302d   v1.18.9-eks-d1db3c
ip-*****.compute.internal   Ready    <none>   2y302d   v1.18.9-eks-d1db3c
ip-*****.compute.internal    Ready    <none>   2y302d   v1.18.9-eks-d1db3c

@rafaelmnatali
Copy link

--set tap.serviceMesh=false --set tap.tls=false

Was trying to install on macOS Sonoma 14.2.1 (M2) and managed to install using:

helm upgrade --install kubeshark kubeshark/kubeshark --set tap.serviceMesh=false --set tap.tls=false

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants