-
Notifications
You must be signed in to change notification settings - Fork 250
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
Unable to launch telegraf docker after capabilities changes #561
Comments
Can you provide me with some more details on how you are running docker?
|
Yes, it on a synology based system:
I'm running docker as root Docker info:
```
# docker info
Client:
Context: default
Debug Mode: false
Server: WARNING: No kernel memory TCP limit support
|
This is looking like influxdata/telegraf#10302 Can you grab the logs from the container as well as the larger docker logs? Also can you get into the container and run
|
Looks like it is a regular file allright
But set/getcap is not happy
Even when using
|
docker.log doesn't contain anything interesting
|
Now I'm wondering if the kernel even has support for
The other thing is to confirm docker is not using aufs:
|
I posted docker info above: #561 (comment) Unfortunately, docker IS using aufs on DSM. When and if Synology will ever decide to upgrade to a better default config is unknown. Historically they have been very to fix anything docker related sadly. In more positive news, the caps are supported:
|
Ah sorry I didn't see the drop down in that comment! At this point I think this means setting these capabilities, while supported by the kernel, is not supported due to the use of aufs. I'm thinking we can wrap the set_cap in at least an error message if it fails to run. |
I think that would be a fine solution. The capabilities are only needed for sending ping packages while not running as root right? |
One capability allows sending ping packages and the other capability allows binding to privileged ports. I have an MP up with the fix, but I will want someone to review/bikeshed the error message with me. |
I had what may be a similar issue using newer version of telegraf on Synology Disktation Docker. As indicated at influxdata/telegraf#10302 I added the user flag as follows Hope this helps! |
I'm actually running into the same issue because of
I'm providing the capabilities needed via
Can we introduce an environment variable to do the setcap?
|
@powersj Great! Works for me. I just did not dig deep enough to find that PR. Thanks. |
When just trying to run the latest
telegraf
docker fails with the following:The latest version that works correctly is 1.20.3
The text was updated successfully, but these errors were encountered: