No space left on device

[Nyholm]

I build plenty of PHP extension and I think it is larger that 5GB.

I get the following output:

Error response from daemon: write /var/lib/docker/tmp/docker-export-122249911/afb84dc4c4395339966/layer.tar: no space left on device tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors

And nothing get's saved. Is there away around this some how? Ie, only save named images? Saved 50% of the images only. Could one increase the cache somehow?

[pbeeson]

At the VERY least, it would be helpful to add to the package README that this is limited to 5GBs of layers. You might think people would know this, but not everyone knows the caps on the github cache.

That said, this works great for my < 5GB projects. Thank you for making it.

[nickjj]

I'm running into this issue in spots that I can't explain. The image being built is 495mb based on the file size reported by Docker when it successfully builds on my dev box. That's the entire image size too, not just 1 layer.

For example, here's a link to a run that worked fine without issues:
https://github.com/nickjj/docker-rails-example/actions/runs/585129343

Then I made a commit that updated 2 text files, and now it says the device has no space left and fails after 45min, that run is at:
https://github.com/nickjj/docker-rails-example/actions/runs/585166083

The commit in question is: https://github.com/nickjj/docker-rails-example/commit/3dac2b1edb5ebad7373c4138ceef4a9bc223b5c7, which is basically no different than the previous commit that worked.

Although it is worth mentioning I did force push that commit that is failing in pipelines due to being out of space. I know it's not a best practice but I had to do it and it was like 1 minute after I pushed it initially on a low traffic repo. Do you think that has an effect?

Edit:

Removing this action results in things working again. Here's a link to a PR in one of my repos https://github.com/nickjj/docker-rails-example/pull/7 that includes a screenshot of the exact disk space error that this action was throwing.

Looking forward to adding it back into my projects but for the moment I've removed it.

[mrserverless]

I think this is the duplicate of #139, I've done some research on this topic and left a comments on workarounds there.