-
Notifications
You must be signed in to change notification settings - Fork 27
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
What's the recommended Disk Space for CodeSpaces? #41
Comments
I found how to clean disk space in codespaces, however the k3d node is evicting most of the pods because it reports as DiskPressure. I think the k3d cluster needs to be configured with appropriate disk space to handle the AIO deployment and additional workloads. |
We have a minimum codespace deployment storage set as 32GB which in my experience should be enough explore-iot-operations/.devcontainer/devcontainer.json Lines 10 to 14 in 9f4bef4
I've seen the low space issue before and it was never clear what causes it since it goes away when I do a full codespace rebuild. Are you seeing this happen on a completely fresh deployment, or sometime afterwards? |
I have seen this behavior more than once in a fresh deployment, I'd say 32Gb is not enough once ARC and AzMonitor are enabled in the cluster. |
Hmm ok. It's easy for me to change the default to be 64GB. You can also resize your codespace in the UI https://docs.github.com/en/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace |
What happened to increasing this? I see you closed the PR @jlian |
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions
The text was updated successfully, but these errors were encountered: