Conky: Sigterm conky when work with docker

Created on 21 Mar 2018  路  5Comments  路  Source: brndnmtthws/conky

conky 1.10.8_pre compiled Mon Mar 12 19:26:00 UTC 2018 for Linux 4.15.8-1-ARCH x86_64

When I restart docker conteiners, I got error

conky: too many interfaces used (limit is 64) 
terminate called after throwing an instance of 'std::system_error'
  what():  Resource deadlock avoided

Maybe its connected with docker network

My config

Most helpful comment

@brndnmtthws I'm still seeing this issue on Ubuntu after installation via apt. It looks like the latest version available as a .deb is 1.10.8 and this fix was included in 1.11

~I don't have any idea how releasing to various package managers works but is there anyway (other than compiling from the source) for Ubuntu / Debian users to get the latest version?~

I just learned something really cool about all these .appimages I've been seeing and ignoring.

I just got the latest release and switched over to it in a few minutes, so nevermind. Thanks for the great tool!

Also: in case anyone else stumbles along this and is yelling "denvercoder9 what did you see?" this is what I did:

  • Went to the releases page here on GH
  • Downloaded the .Appimage file from the latest release assets
  • Made the file executable with chmod +x conky-x86_64.AppImage
  • Ran it with ./.conky-x86_64.AppImage
  • And then to make it run like the package would normally I renamed it: mv conky-x86_64.AppImage conky and moved into into a bin directory on my path.
  • Now it runs with conky like the apt install would
  • (Also I uninstalled the apt-installed version before any of that)

All 5 comments

Indeed there is an issue when using Docker.
In Conky's code, a static array of 64 elements is created to store the internet interfaces of your machine. When you use docker, virtual ethernet networks are created with random names. When Conky reads a new interface, it adds it to the array, but there is no process to remove them. Therefore, when the 65th interface is discovered, it tries to add it outside of the array and crashes.
I am currently working on a solution for that but everything I tried is not working very well. I'll tell you if I can come with a solution.

Fixed in my fork. I opened a pull request.

I was experiencing this issue too and realized it must be related to Docker's virtual interfaces. Glad to see it's already reported.

Fixed with #479.

@brndnmtthws I'm still seeing this issue on Ubuntu after installation via apt. It looks like the latest version available as a .deb is 1.10.8 and this fix was included in 1.11

~I don't have any idea how releasing to various package managers works but is there anyway (other than compiling from the source) for Ubuntu / Debian users to get the latest version?~

I just learned something really cool about all these .appimages I've been seeing and ignoring.

I just got the latest release and switched over to it in a few minutes, so nevermind. Thanks for the great tool!

Also: in case anyone else stumbles along this and is yelling "denvercoder9 what did you see?" this is what I did:

  • Went to the releases page here on GH
  • Downloaded the .Appimage file from the latest release assets
  • Made the file executable with chmod +x conky-x86_64.AppImage
  • Ran it with ./.conky-x86_64.AppImage
  • And then to make it run like the package would normally I renamed it: mv conky-x86_64.AppImage conky and moved into into a bin directory on my path.
  • Now it runs with conky like the apt install would
  • (Also I uninstalled the apt-installed version before any of that)
Was this page helpful?
0 / 5 - 0 ratings

Related issues

Microcrap picture Microcrap  路  4Comments

nwwt picture nwwt  路  5Comments

ghost picture ghost  路  4Comments

moyamo picture moyamo  路  3Comments

Microcrap picture Microcrap  路  4Comments