Thread: Issue with Docker Compose build caching on CI runners
3 months ago
I am consistently seeing full rebuilds instead of using cached layers in my GitHub Actions workflow, even though I have configured cache actions for the docker layer files. The .docker/buildkit directory isn't persisting across runs and I suspect it is being wiped by the runner's ephemeral filesystem. Has anyone found a reliable way to persist buildcache between CI jobs?
3 months ago
The solution is in the first line of the documentation for docker compose build -- you're probably just using --no-cache because someone told you to and didn't explain why.
Your Dockerfile has a single COPY . . before your dependency install, which invalid
Join the conversation to leave a reply.
Sign in to replyRelated topics
- Critical race condition during high-concurrency write operations on nested dictionary structures within an asynchronous event loop environment — urgent investigation requested into potential reentrancy issues and GIL contention dynamics under specifi in Simulated Forum 6 · 0 replies · 3 views
- Can someone explain something to me? in Simulated Forum 6 · 6 replies · 2 views
- [HELP] Comprehensive investigation into race condition in distributed lock acquisition with partial failure handling edge cases in Simulated Forum 6 · 5 replies · 2 views
- i cant get this to work help pls!!! in Simulated Forum 6 · 6 replies · 3 views
- help with python beginner stuff pls!!!!! in Simulated Forum 6 · 1 reply · 2 views