-
Notifications
You must be signed in to change notification settings - Fork 440
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
Auto-instrumentation cp operation not permitted #2726
Comments
cc) @iblancasa |
@pavolloffay thanks for the heads-up! Can you check if #2695 fixes your issue? |
Looks like it is not resolved yet. Reproduced the issue with the ffg:
Container user Error
|
|
Hi @iblancasa , We are encountering the same issue when trying to instrument Nginx: Some additional information:
Are there any suggestions on how to fix this? |
Would you be able to provide a reproducer? @jurgenroels |
@iblancasa What can we use to make the reproducer? This way we can see what it is collecting and if we can share it. |
@jurgenroels if you can reproduce it using kind and provide the image, Instrumentation CR and Deployment used it would help. |
@iblancasa in attachment you can find the files to reproduce. We also tested other Nginx images |
Please, provide one of the images or Dockerfiles of the container image to instrument. |
This is the link: https://hub.docker.com/r/nginxinc/nginx-unprivileged |
My guess would be "cp -ar ..." needs to be changed to "cp -r ..."
This has been done for other instrumentations but apparently not for nginx. |
I was not able to reproduce but... yes. There were other instrumentation where something similar happened. |
Thanks @excitedbumpkin and @iblancasa |
I would like to reopen this one. "cp: can't preserve permissions of '/otel-auto-instrumentation-nodejs/.': Operation not permitted" This will fail on all containers running as a non-root user. |
Please, create a new issue for that. It should be a different issue because the NodeJS libraries are copied like: Command: []string{"cp", "-r", "/autoinstrumentation/.", nodejsInstrMountPath}, |
Component(s)
instrumentation
What happened?
Description
when I add annotation to our .net application, it is not able to inject the library and produces the error logs from init container.
I set up
USER 64189
in Dockerfile. I'm running pod with non-root user, the followingsecurityContext
options are set in our helm deployment template.allowPrivilegeEscalation: false
privileged: false
readOnlyRootFilesystem: false
runAsNonRoot: true
Steps to Reproduce
Enable RunAsNonRoot option
Expected Result
inti container copy library to the application pod without errors
Actual Result
Kubernetes Version
1.26.9
Operator version
0.93.0
Collector version
0.93.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: