3 ms·

Why not leverage Docker's built-in image layer caching?

• kentt 10y ago
  I think the idea here is that the docker level caching isn't well suited for this. Eg for us we install all relevant gems with `bundle install`. If you update one gem, that the whole layer is rebuilt. Since the whole `bundle install` layer is rebuilt, every gem is fetched again from rubygems. Yarn works the same.
  • morgante 10y ago
    Having a separate FROM image doesn't help that situation either, since you have to rebuild it.
    • skj 10y ago
      Couldn't you FROM and then update? I'm not a ruby expert but I'd hope that it could be incremental.
• puzzle 10y ago
  That might be less effective if you can't guarantee that all the builds end up always on the same node.