Docker Cache BUNDLE INSTALL not working

Anybody knows how to make BUNDLE INSTALL Cache’ing work in latest DOCKER release?
I’ve tried so far:

1. 
WORKDIR /tmp 
ADD ./Gemfile Gemfile
ADD ./Gemfile.lock Gemfile.lock
RUN bundle install

2.
ADD . opt/railsapp/
WORKIDR opt/rails/app
RUN bundle install

None of them work, it still runs “BUNDE INSTALL” everytime from scratch without Gemfile being changed.

  • Pika to RabbitMQ connection failure using Raspberry PI and Docker container
  • Reliable centralized logging in Kubernetes/Docker with Elastic Stack
  • .Net Core Machine Key alternative for webfarm
  • Docker Error getting events from daemon: EOF
  • Create a ASP.net Core project with Docker Support for Windows
  • Docker does not auto update DNS server details in /etc/resolv.conf
  • Anyone knows how to make Caching for bundle install work correctly?

    Cheers,
    Andrew

  • Install Gitlab with disabled sign up
  • getting Docker script to load with git-bash in ConEmu/Cmder
  • Docker: How to create a stack, multiple images or one base image?
  • Elasticsearch in docker container cluster
  • Switching app versions with docker container
  • PyCharm remote debug in a docker container
  • 3 Solutions collect form web for “Docker Cache BUNDLE INSTALL not working”

    Each time you change any file in your local app directory, the cache will be wiped out, forcing every step afterwards to be re-run, including the last bundle install.

    The solution is don’t run bundle install in step 2. You have already installed your gems in step 1 and there is little chance the Gemfile will change between step 1 and step 2 ;-).

    The whole point of step 1 is to add your Gemfile, which should not change to often, so you can cache it and the subsequent bundle command before adding the rest of your app, which will probably change very often if you are still developing it.

    Here’s how the Dockerfile could look like:

    1. 
    WORKDIR /tmp 
    ADD ./Gemfile Gemfile
    ADD ./Gemfile.lock Gemfile.lock
    RUN bundle install
    
    2.
    ADD . opt/railsapp/
    WORKIDR opt/rails/app
    

    Versions of Docker before 0.9.1 did not cache ADD instructions. Can you check that you’re running a version of Docker 0.9.1 or greater?

    Also, which installation of Docker are you using? According to this GitHub issue, some users have experienced cache-busting ADD behavior when using unsupported Docker builds. Make sure you’re using an official Docker build.

    ADD caching is based on all the metadata of the file, not just the contents.

    if you are running docker build in a CI-like environment with a fresh checkout, then it is possible the timestamps of the files are being updated which would invalidate the cache.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.