title: Dockerized Rails 5 RC1 application not picking up updates to controllers and models in development
body: <p>I have quite a bit of experience developing Rails 4 apps on Mac OS X + Docker Machine + Docker Compose, but something has changed with how Rails 5 is caching files in the development environment (currently testing with RC1).</p>
  
  <p>After starting the application with <code>docker-compose up</code>, the application runs normally in development mode.</p>
  
  <p>But if I make a change to a controller or model, the only way I can get that reflected in the application is to stop the server and start it back up.</p>
  
  <p>So now my workflow looks something like this when I need to make a change to a controller or model:</p>
  
  <ol>
  <li>Make change to controller/model class.</li>
  <li>Stop server with <code>Ctrl + C</code>.</li>
  <li>Start server back up with <code>docker-compose up</code>.</li>
  <li>Wait on the server to start up.</li>
  <li>Run whatever I was running in the browser.</li>
  </ol>
  
  <p>To say the least, needing to do steps 2-4 is annoying and not what I'm accustomed to from Rails 4.</p>
  
  <p>I went a step further and uninstalled Spring using the <a href="https://github.com/rails/spring#removal" rel="noreferrer">Removal instructions</a>, but I still get the same behavior.</p>
  
  <p>I also searched for any settings that I could find in <code>config/environments/development.rb</code> related to the Rails runtime's iron grip on the model and controller classes, and I couldn't find anything. (I assume that it really wants to rely on watching the filesystem in order to selectively load changes, and something isn't being picked up from a change on Mac to VirtualBox.)</p>
  
  <p>Any other ideas on what I can try? Or are there any new settings related to how this more aggressive caching works?</p>