Guides
How to use container jobs effectively
Container jobs give reproducibility but break caching.
5 min read
Container jobs give reproducibility but break caching.
Why it happens
Paths inside the container differ from the host paths the cache action sees.
How to fix it
- Reference container paths in cache keys, not host paths
- Pin the container by digest for reproducibility
- Weigh the image pull cost against the reproducibility benefit for short jobs
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.