Replies: 3 comments 2 replies
-
Hi @cep21, |
Beta Was this translation helpful? Give feedback.
-
Hey @cep21, I know this issue is quite old, but if you're still looking for a solution, you could try an alternate runner such as https://github.com/runs-on/runs-on, which allows specifying disk size at runtime. For instance for a 100GB disk:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Lots of people are running short on disk space running github actions. This is creating hacks like this. https://github.com/ThewBear/free-actions You can see lots of them in github if you search for the rm string.
https://github.com/search?l=YAML&q=rm+%2Fusr%2Fshare%2Fdotnet&type=Code
They are often look like this: https://github.com/VirtusLab/intellij-pants-plugin-tests/blob/1b0d2d685e80dfa6ec59939e0d3c832a7f8e4f15/.github/workflows/prepare-image.yml#L15
It seems like a hack to
rm
the directories that happen to be taking a lot of space, and probably something that's not consistent from one build to the next in the future. It may be worth a way to specify a minimal version to use, for people that need the extra disk space.Some more follow up links here:
Beta Was this translation helpful? Give feedback.
All reactions