Codespaces corruption on resumption (march 3rd) with k8s using docker-in-docker #153724
Replies: 1 comment
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Yesterday, all my Codespaces I created were corrupted on shutdown and resume. I was deploying a kubernetes cluster using docker in docker and then deploying workloads.
On resumption, the disk would either reduce to 6GB disk and hit 100% usage and everything would just fail, or it would complain about no
codespace
user existing and would revert to recovery mode.Testing again this morning, it appears that it's working again, but I want to confirm that there was a backend Codespaces issue that was resolved so I can rule out any possible issue on my end.
Beta Was this translation helpful? Give feedback.
All reactions