March-26th-2018, 11:22 AM
Hello Thomas,
interesting aspect. We have never thought about an issue that a docker logging file could produce an issue.
At the current stage I even don't know if a container really stops working in the case the SD card is getting full, but I trust your experience cause I don't have any life example of a container doing the same.
Today there is no possibility I see no possibility to disable this logging mechanism. I agree that this is getting critical in case a container really stops its operation.
Since in a container it is still under you control what is sent to the STDOUT, I would recommend to insert an environment variable "DEBUG" for example and test in all echoing applications you are running the existence of it to decide whether or not to output data on STDOUT. Other methods I don't see right now.
interesting aspect. We have never thought about an issue that a docker logging file could produce an issue.
At the current stage I even don't know if a container really stops working in the case the SD card is getting full, but I trust your experience cause I don't have any life example of a container doing the same.
Today there is no possibility I see no possibility to disable this logging mechanism. I agree that this is getting critical in case a container really stops its operation.
Since in a container it is still under you control what is sent to the STDOUT, I would recommend to insert an environment variable "DEBUG" for example and test in all echoing applications you are running the existence of it to decide whether or not to output data on STDOUT. Other methods I don't see right now.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
