title: Webpacker & Rails Asset Pipeline in Docker - View is not pointing to updated JS asset
body: <p>I am running a Rails app in a Docker container but am struggling with my development environment as I can't reliably get javascript changes to propagate through to my app running at localhost.</p>
  
  <p>Description of steps to identify problem:</p>
  
  <ul>
  <li>If I refresh the view I can see in the console that webpacker is compiling.</li>
  <li>It generates a new cache-busted asset in public/packs <code>admin-7c69920b702f68258e99.js</code></li>
  <li>The manifest.json reflects this update <code>"admin.js": "/packs/admin-7c69920b702f68258e99.js"</code></li>
  <li>I can refresh the view repeatedly and yet the network tab shows that the old asset is called <code>admin-4cf5f7c7d6c5ad665fc6.js</code>. </li>
  </ul>
  
  <p>I've tried the following process but it doesn't trigger a refresh of the assets even with cache disabled.</p>
  
  <ul>
  <li>Refresh the view in the browser to trigger webpack compile</li>
  <li>Restart the Rails server by crashing out of Docker and running <code>docker-compose up</code></li>
  <li>Refresh the view</li>
  </ul>
  
  <p>I typically have to stop and start the Rails server a second time to trigger the refresh of assets. This feels a bit too voodoo-like for an effective development environment.</p>
  
  <p>I would like to find a way to reliably ensure that the latest assets are reflected in my development environment without having to manually keep tabs on the asset file names to confirm the refresh has happened. </p>
  
  <p>Is there a trick to getting the assets to reload that I might be missing?</p>
  
  <p>I'm using ruby:2.3.7 and Rails 5.2.2.1</p>