chore: optimize pipeline by caching docker image layers#3158
Merged
Ziinc merged 1 commit intoLogflare:mainfrom Feb 13, 2026
Merged
chore: optimize pipeline by caching docker image layers#3158Ziinc merged 1 commit intoLogflare:mainfrom
Ziinc merged 1 commit intoLogflare:mainfrom
Conversation
I have considered using this [action](https://github.com/marketplace/actions/docker-layer-caching), I discarded it because it is not from the offical docker team. This [guide](https://www.blacksmith.sh/blog/cache-is-king-a-guide-for-docker-layer-caching-in-github-actions) gives a good overview on how to accomplish this and explains why caching images from the docker registry is in practice worst than just pulling. I am essentially following this [approach](https://cicube.io/blog/optimize-docker-builds-github-actions-cache/).
nelsonmestevao
force-pushed
the
ne/caching-docker
branch
from
6737100 to
73c16fb
Compare
Ziinc
approved these changes
Feb 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have considered using this action, I discarded it because it is not from the official docker team.
This guide gives a good overview on how to accomplish this and explains why caching images from the docker registry is in practice worse than just pulling.
I am essentially following this approach.
Performance Comparison
Previously, this was taken ~9 minutes to setup the supabase services.
Now, it is taking around ~7 minutes by caching the layers of the image build.