i was just happy/lucky finding a way to bypass the issue. i also tried different appenders in the logback.xml to be sure that it's not a problem with the daily/filesize-rollover.įor the moment i just turned off Use gRPC FUSE for file sharing on my local machine, which is fine, since this is only a dev-notebook.ītw: i have no clue about this cfg-setting and it's pro- and cons. at the moment i do not have a dummy-jar doing this which i could provide, but when i find the time i will do so.
When i test the way you described, i also can NOT reproduce the issue.įor the Dockerfile: i do have a java-application using slf4j and logback to write to the logfile. Once the Console.app has opened the logfile (and i then restart the container) i also do see the expected behaviour of loglines getting appended. Maybe this issue does not occur on Big Sur anymore.Īre you sure you have Use gRPC FUSE for file sharing turned on in your Docker.App preferences? It can be "solved" by unchecking the Use gRPC FUSE for file sharing !!
#Cons of docker for mac for mac
The problem is seen since updating to Docker Desktop for Mac v.2.4.0.0 (48506) stable. When the logfile is already opened in Console.app and the Container is started afterwards the logs can be observed as long as the Console.app is kept open on the logfile. When using tail -f logfile.log or `vi log file.log' the behaviour is as expected and the file does not get changed. When opening the logfile with Console.app the log file becomes 0 Byte immediately. Opening the logs on the host (MacOS 10.15.7) with Console.app or TextEdit.app should just show the content of the log file.
At the end of the day, Docker is still Linux-only. But it actually uses virtual machines to run on non-Linux platforms.
A Java-App uses logback to create logs there. Docker now advertises itself as supporting Windows and Mac OS X as well as Linux.
0 kommentar(er)
