You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing issues with running a LogDNA logspout Docker container on my fairly old Rancher setup (Rancher v1.6.4).
The issue is a constant CPU usage spike when starting a logspout container. It basically takes over the CPU.
Found this related issue here gliderlabs/logspout#246 where people are actually blaming Docker itself for this problem and are suggesting to use logspout v3.1 as a workaround.
Any suggestions how to run v3.1 of logspout with LogDNA in a Rancher setup?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi there. We think we can find some time to address this. Frankly, our module being pinned to logspout's latest has been something that feels like we should have addressed a while ago.
Thanks for pointing this out, and we'll try and get on it for you.
Hello there,
I am experiencing issues with running a LogDNA logspout Docker container on my fairly old Rancher setup (Rancher v1.6.4).
The issue is a constant CPU usage spike when starting a logspout container. It basically takes over the CPU.
Found this related issue here gliderlabs/logspout#246 where people are actually blaming Docker itself for this problem and are suggesting to use logspout v3.1 as a workaround.
Any suggestions how to run v3.1 of logspout with LogDNA in a Rancher setup?
Thanks.
The text was updated successfully, but these errors were encountered: