[SOLVED] STDOUT logging when container is started with -I and some CMD

[Thomas]

Hi Armin,

I ran into an issue where the netPi stopped working and the SD-card was completely full. I assume it was because STDOUT and STDERR are logged when a container is started with interactive shell and a CMD which writes to STDOUT and STDERR. The logs can be accessed through portainer, container details. Is there a possibility to clear the logs or to limit the size of the log-files when the container is created?
I had to delete and recreate the container to get it up and running again. It might be desirable to have the logs, but the netPi should not stop working because of it. Especially not when running in an industrial application.

Best regards
Thomas

[Armin@netPI]

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.

[Armin@netPI]

With netPI firmware V1.1.3.0RC3 this problem is solved and the log file is limited to a size of 1Mbyte now.