-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"You are running out of disk space" Error. How can I fix this? #2840
Comments
Hello, @jessehui As a workaround:
|
@al-cheb Thank you for your reply. I would give it a try. I am just curious whether this limitation is added recently? Because we never encounter this error running the same workflow before. |
@al-cheb is there any way that you can provide more disk space to the customer? we do multistage docker build and 14 gb is too small for us, we are using 'ubuntu-latest' ado / azure pipelines .. not github actions
|
@jessehui , this limitation has always existed but previously, we have provided a bit more free space. Sometimes, image can have ~15-20 GB of free space and this volume can be changed without notice. We only guarantee that images contain at least 14 GB of free space. @arroyc , unfortunately, no. Only workarounds that Aleks has shared above |
@maxim-lobanov thanks for responding ... i just found following information in one of our builds ... its not even 14G ... its less than 10GB .. can you please confirm that? I'm assuming we are only using /dev/sda1
|
@al-cheb @maxim-lobanov Thank you for your help. We've managed to work this out. You may close this issue. |
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes openzfs#11826
Recently we've been running out of free space in the ubuntu 20.04 environment resulting in test failures. This appears to be caused by a change in the default available free space and not because of any change in OpenZFS. Try and avoid this failure by applying a suggested workaround which removes some unnecessary files. actions/runner-images#2840 Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #11826
# 清理 action 镜像磁盘空间 # actions/runner-images#2840 sudo rm -rf /usr/share/dotnet sudo rm -rf /opt/ghc sudo rm -rf "/usr/local/share/boost" sudo rm -rf "$AGENT_TOOLSDIRECTORY"
Our CI jobs constantly fail due to the lack of disk space, so free up some space by removing unnecessary directories following suggestions at actions/runner-images#2840
**What problem does this PR solve?**: Noticed `no space left on device` [error messages](https://github.com/nutanix-cloud-native/cluster-api-runtime-extensions-nutanix/actions/runs/9008250141/job/24773942020?pr=638#step:5:276) in e2e tests which cases the tests to fail. This PR runs a step to clean up the disk, replicated from upstream issue actions/runner-images#2840 **Which issue(s) this PR fixes**: Fixes # **How Has This Been Tested?**: <!-- Please describe the tests that you ran to verify your changes. Provide output from the tests and any manual steps needed to replicate the tests. --> **Special notes for your reviewer**: <!-- Use this to provide any additional information to the reviewers. This may include: - Best way to review the PR. - Where the author wants the most review attention on. - etc. -->
For the benefit of those who come across this several years later, as I did, here's a more up-to-date list of big things that you could remove at the start of a build:
|
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io>
[ upstream commit e553bd2 ] We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: gray <greyschwinger@gmail.com>
[ upstream commit e553bd2 ] We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: gray <greyschwinger@gmail.com>
[ upstream commit e553bd2 ] We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: gray <greyschwinger@gmail.com>
[ upstream commit e553bd2 ] We are having the below failure due to no disk space, it seems like we can remove pre-installed software and language runtimes, which are not use in Cilium, to reclaim more disk space. Alternative option is to bump the runner, but it might not be the best resource and cost utilization. Relates: https://github.com/cilium/cilium/actions/runs/10300396788 Relates: actions/runner-images#2840 (comment) Signed-off-by: Tam Mach <tam.mach@cilium.io> Signed-off-by: gray <greyschwinger@gmail.com>
Description
![截屏2021-03-04 下午5 48 22](https://user-images.githubusercontent.com/13930406/109945056-d8ca8880-7d11-11eb-89d7-1f7dd37bf4a3.png)
The previous execution of this action never gives an error like this.
I think the reason is that the virtual environment is changed. But I am not sure. My question is whether there is a fix for this? I don't want to change the yaml file. Thank you. The action can be found here: https://github.com/occlum/occlum/actions/runs/619537350
Virtual environments affected
Image version
Image version where you are experiencing the issue.
Environment: ubuntu-18.04
Version: 20210219.1
The text was updated successfully, but these errors were encountered: