-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How is docker run cache handled across rebuilds #482
Comments
This type of cache is internal and as the GitHub Runners are ephemeral the BuildKit state volume is lost. But if you have a self-hosted runner it should be reused if you stick to the same builder. I guess we could handle a specific cache for this volume in the GitHub Action itself with @actions/cache. cc @tonistiigi |
This would be amazing for my |
Since docker/buildx#672 BuildKit state is saved in a named volume. We should be able to cache it and mount it back but that would require some changes in the setup-buildx-action. Will think about it. |
Tracked in docker/setup-buildx-action#122 |
For example I have the following lines in the dockerfile:
How are those cache lines handled across rebuilds? I'm missing details in the documentation to understand what's happening.
The text was updated successfully, but these errors were encountered: