-
Notifications
You must be signed in to change notification settings - Fork 12
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
Bug: /otelcol-custom: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /otelcol-custom) #43
Comments
After updating the version from 0.75 to 0.86 for OTEL it still gives errors
|
@damemi Can you please help me here |
Sorry, damemi is out. I'll take a look. |
Which sample did you apply, and which collector did you apply? |
Hi @dashpole I have rerun entire thing with everything rolled back to main branch. I still get the same error
|
What kind of GKE cluster are you running it on? |
I am running GKE Autopilot |
gcloud auth login
gcloud container clusters create-auto builder-bug --region us-east1
git clone https://github.com/GoogleCloudPlatform/opentelemetry-collector-builder-sample.git
cd opentelemetry-collector-builder-sample
make setup-artifact-registry
cd build/local
make docker-build
make docker-push
cd ../../deploy/gke/simple/
export GCLOUD_PROJECT=<the Google Cloud project ID to which your IAM service account belongs>
export PROJECT_ID=<your Google Cloud project ID>
gcloud iam service-accounts create otel-collector --project=${GCLOUD_PROJECT}
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member "serviceAccount:otel-collector@${GCLOUD_PROJECT}.iam.gserviceaccount.com" \
--role "roles/logging.logWriter"
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member "serviceAccount:otel-collector@${GCLOUD_PROJECT}.iam.gserviceaccount.com" \
--role "roles/cloudtrace.agent"
gcloud projects add-iam-policy-binding $PROJECT_ID \
--member "serviceAccount:otel-collector@${GCLOUD_PROJECT}.iam.gserviceaccount.com" \
--role "roles/monitoring.metricWriter"
gcloud iam service-accounts add-iam-policy-binding "otel-collector@${GCLOUD_PROJECT}.iam.gserviceaccount.com" \
--role roles/iam.workloadIdentityUser \
--member "serviceAccount:${GCLOUD_PROJECT}.svc.id.goog[otel-collector/otel-collector]"
export OTEL_NAMESPACE=otel-collector
kubectl create namespace $OTEL_NAMESPACE
kubectl create serviceaccount otel-collector -n otel-collector
kubectl annotate serviceaccount otel-collector \
--namespace $OTEL_NAMESPACE \
iam.gke.io/gcp-service-account=otel-collector@${GCLOUD_PROJECT}.iam.gserviceaccount.com
kubectl create configmap otel-config --from-file=./otel-config.yaml -n $OTEL_NAMESPACE
kubectl apply -f manifest.yaml -n $OTEL_NAMESPACE
kubectl logs deployment/otel-collector -n otel-collector Output of
I am not able to reproduce your issue. Can you follow the steps above exactly (filling in the project), and let me know if you are still able to reproduce the issue? |
let me try this @dashpole |
Hi @dashpole , I followed the above steps and get the following error. I ran this from cloud shell, so local environment should not be a problematic. You can checkout my activity from cloud shell here
|
Let me try from cloud shell. Based on golang/go#58550 this has something to do with the CGO_ENABLED and the go version. I'm also going to try updating the collector version and go version to see if that helps. |
One other question while I work on the above: Did you enable any options when you created your GKE Autopilot cluster? |
@dashpole No Used your command |
I was able to reproduce this in cloud shell, so that seems to be part of the issue. |
Using cloud build from the cloud shell does not help |
Confirmed that #48 fixes this issue |
Once I create the image using cloud build I get the following issue
arjunvijay@cloudshell:~/.../gke/simple (arjun-demo-123)$ kubectl logs otel-collector-97fd46647-rhhg4 -n $OTEL_NAMESPACE
/otelcol-custom: /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.32' not found (required by /otelcol-custom) /otelcol-custom: /lib/x86_64-linux-gnu/libc.so.6: version
GLIBC_2.34' not found (required by /otelcol-custom)The text was updated successfully, but these errors were encountered: