Open
Description
Sometimes container action fails, because of "No space left on device" error. Here why:
Action "whoan/docker-build-with-cache-action@v3" works like that:
- pull images from (private) registry
- build new images using pulled layers (
--cache-from=option) - push new images to the registry
The assumption is that most of the old layers are used in always all new builds (because deepstate-base Dockerfile and fuzzers installation scripts change hardly ever). That seeds up build processes significantly.
The problem is that sometimes, I don't know why, old layers are not used and whole build runs starts the scratch. So there are pulled old layers and new, freshly build code. And that takes too much memory.