Open bran1501 opened 3 months ago
If you are facing the PUB_KEY error try running the below command
rm /usr/share/keyrings/cloud.google.gpg && rm /usr/share/keyrings/cloud.google.gpg~
This removes any existing Google Cloud public key files, both the primary and backup (~) versions.wget -q -O - https://packages.cloud.google.com/apt/doc/apt-key.gpg | gpg --dearmor -o /usr/share/keyrings/cloud.google-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/cloud.google-archive-keyring.gpg] http://packages.cloud.google.com/apt cloud-sdk main" | tee /etc/apt/sources.list.d/google-cloud-sdk.list
apt-get update
Hi @ganeshardlkar I checked and I don't have those keyrings, however I downloaded the GPG, install the repo and updated Ubuntu, but the issue persists Reading package lists... W: GPG error: https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DDCAE044F796ECB0 E: The repository 'https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease' is not signed.
Unable to use the host's package manager configuration to automatically install kernel headers for the Linux distro 'debian'.
Please reach out to support and include this log in its entirety so we can diagnose and fix the problem.
In the meantime, please install kernel headers manually on each host before running the Kernel Collector.
To manually install kernel headers, follow the instructions below:
for Debian/Ubuntu based distros, run:
sudo apt-get install --yes "linux-headers-uname -r
"
for RedHat based distros like CentOS and Amazon Linux, run:
sudo yum install -y "kernel-devel-uname -r
"
Hi @bran1501 were you able to find any solution to this issue? If yes, request you to comment down your approach. Thanks
@ganeshardlkar I tried different approaches but it looks like a development issue since it hasn't been updated to lastest ubuntu releases.
Hey 🙋♂️ I'm on Minikube and get that error. Any update on that issue ?
Edit : Tried to switch from minikube/dockerd to rancher/containerd, seems better but have another issue on the k8s-collector/k8s-watcher. Avoid k8s docker-api base like minikiube which prevent to access ebpf in docker engine from the host ?
2024/11/19 09:29:39 [Error]: Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp [::1]:8712: connect: connection refused"
and also issue on the reducer
2024-11-19 09:38:43.848663+00:00 error [p:1 t:19] Logging core failed to publish internal metrics writer stats
and also kernerl-collector
END log from kernel headers resolution with error 'unsupported_distro':
Edit2 : Tried Grafana Beyla and worked like a charm
What happened?
Description
While implementing the ebpf helm chart from https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-ebpf/values.yaml I configured the endpoint but once it starts, the daemonset my-opentelemetry-ebpf-kernel-collector fails returning these errors: Err:1 https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DDCAE044F796ECB0
Reading package lists... W: GPG error: https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DDCAE044F796ECB0 E: The repository 'https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease' is not signed.
Steps to Reproduce
helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts helm repo update open-telemetry sudo apt-get install --yes linux-headers-$(uname -r) ebpf.yaml endpoint: address: " my-splunk-otel-collector.otel.svc.cluster.local" kernelCollector: image: tag: "v0.10.2" name: opentelemetry-ebpf-kernel-collector
helm --namespace=otel install my-opentelemetry-ebpf -f ebpf.yaml open-telemetry/opentelemetry-ebpf
Expected Result
Pod should be able to download the respective dependencies.
Actual Result
Pod not able to resolve the dependencies.
eBPF Collector version
0.10.2
Environment information
Environment
OS: christhianb@christhianb-k8s:~$ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS" NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal
eBPF Collector configuration
Log output
Additional context
No response