{Solved] Docker image utilization/logs, bypassing 50m limit

[dstark4]

I have a server that is experiencing a problem where the lancache container is bypassing the 50m limit set in docker settings. I have also add the "--log-opt max-size=50m --log-opt max-file=1" to the extra parameters field.

 

Is there another recommended command to add? I know its the access.log that is the culprit. My googlefu keeps pointing me to posts adding the parameters to the container. Such as Squid's excellent docker faq and even red hat articles

 

Edited January 8, 2021 by dstark4
Solved

[Squid]

The thing about the options in docker settings is that they only take effect on new containers added.   Any pre existing containers won’t have the log take effect.   The extra parameters however should take effect.  (I think)

[dstark4]

That's the thing, log file size limit was set when I first configured this server. I have added a path to the container to send that log to share outside of the docker image, but that's a bandaid. The file has grown to about 1gig in 6hrs.

 

I am unsure what to do otherwise

[dstark4]

I believe I have narrowed down the problem, the lancache container has a config file for sni, which is not following the above max file size.

 

To fix the problem I have edited the container to have a path for /etc/nginx/stream-enabled/ to appdata. I have edited the conf file to commit out the offending access log.

 

So far nothing is being written, I will watch the docker img to make sure nothing else is being written. I will mark this post solved in a couple days if nothing else occurs.