Caching PNPM Modules in Docker Builds in GitHub Actions

1. gha-docker-npm-caching-example

   1 1 1 5.2 Dockerfile

   Example of caching NPM modules within Docker with GitHub Actions

   

   You can use reproducible-containers/buildkit-cache-dance to reuse cached files in your Docker build and an action like tespkg/actions-cache or actions/cache to persist the cache externally. See GitHub repo for an example setup.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. buildkit

   2 62 8,559 9.8 Go

   concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit

   

   The currently proposed solution is to allow Docker to bind the cache directory in the build to a directory on the host. This way the cache could be persisted externally. However, this issue has been opened for almost 4 years (May 27, 2020) with no clear answer as to whether it'll be implemented any time soon.

4. buildkit-cache-dance

   3 1 198 6.5 TypeScript

   Save `RUN --mount=type=cache` caches on GitHub Actions ( Forked from https://github.com/overmindtech/buildkit-cache-dance )

   

   This is where the reproducible-containers/buildkit-cache-dance GitHub Action comes to the rescue! This Action is able to extract the files from the Docker build so they can be persisted on an external storage like S3 and is the approach recommended on the official Docker documentation.

5. actions-cache

   4 1 85 5.1 TypeScript

   Cache to S3 storage with official actions/cache@v2 fallback

   

   tespkg/actions-cache: Cache to S3 storage with official actions/cache@v2 fallback

Suggest a related project