-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman endpoints cfg issue #34522
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for raising this. The connection strategy was mostly copy/paste from https://github.com/containers/podman/blob/main/pkg/bindings/connection.go#L90. And you are correct, the implementation is adding an extra "/" for non-absolute paths unix sockets. I reckon that both forms should work in most situations, but relying on Does your socket exist in |
Yes, looks all good for me - I have added below debug logs in same shell where otelcol is executed later
and output
Ok --Path was wrong. |
Great we found out the root problem, do you think we can close the issue? |
I still think the message and the wrong path composed because of some strange fallback default is completely misleading and shall be improved |
Although the receiver is just propagating the error retrieved from the @cforce Would you be interested in opening a PR to improve the error message? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/podman
What happened?
Description
The endpoint used differs from the one configured. An exrta "/" is injected for unknown reasons
"dial unix /run//podman/podman.sock: "
but configured is
"endpoint: unix://run/podman/podman.sock"
Maybe docs are buggy and we ned to use escape for ":" or /"?
see https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/podmanreceiver
Collector version
0.106.1
Environment information
Environment
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: