Clarification on cache location about docker-build-with-cache-action HOT 2 CLOSED

Hi @quoimec . The cache is sent to the registry you configure in the action inputs, and you can choose GitHub like this:

- uses: whoan/docker-build-with-cache-action@v5
  with:
    username: whoan
    password: "${{ secrets.GITHUB_TOKEN }}"
    registry: docker.pkg.github.com
    image_name: hello-world

The cache are the tagged *-stage images. If most of your build time is spent downloading the image set in the FROM statement, this action won't help as the purpose is to cache the build steps, so you download each step instead of building it again which is usually faster.

from docker-build-with-cache-action.

Ah ok all good, looks like this actions is for a different use case then. For reference, this was the GH caching that I was talking about where data is cached in the git repo: https://docs.github.com/en/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows. Will have to use the GH action by the looks of it. Cheers anyway and thanks for the reply!

from docker-build-with-cache-action.