title: Docker logs stop logging to console when followed
body: <p>I am running into what feels like <a href="https://en.wikipedia.org/wiki/Observer_effect_(physics)" rel="nofollow noreferrer">the observer effect</a> with regards to my Docker logs. I am running <code>docker-compose logs -f containerName</code> and the logs begin to print to my console. I happen to be using hot reloading in my JavaScript app such that modifying a file then saving it will trigger a hot reload which will be documented in the logs I am following. The hot reloading is controlled via gulp tasks that call on browserSync. </p>
  
  <p>The hot reloading seems to appear in the logs as expected if I run it only a couple of times. If I wait an extended period of time (minutes), triggering a hot reload no longer appears in the logs. If I quit following the logs then immediately begin following them again, I can see that the most recent hot reload was logged, it just was not being previously displayed. This leads me to believe that something probably related to processes and file descriptors is causing this behavior. </p>
  
  <p>Almost as if the process that is running the log following no longer is receiving the output from the logs. It also seems to happen inconsistently in that different numbers of hot reloads will get logged before they cease to be logged each time I run the docker logging command. Any suggestions to as how I can ensure that my logs are always printing new log info would be appreciated. Additionally an explanation as to what is causing this underlying behavior would be a bonus.</p>
  
  <p>Running "Docker Desktop" (formerly called Docker for Mac?)</p>
  
  <p>Version 2.0.0.0-mac78 (28905)</p>
  
  <p>Engine: 18.09.0</p>