Code space attempts restart, event though container has been deleted very long time. #150810
Replies: 2 comments
-
💬 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.
-
I have understand the way storage arose, it is normal. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
https://github.com/settings/security-log
From the log, storage usage of code space still arising even though not connecting to it.
The codespace development container created from the Docker file was deleted two weeks ago, but from the log, the deleted container is still trying to restart, occupying a lot of storage resources, making it impossible to use the codespace container for development some time.
This container is mainly used to develop a graphics renderer server for the open source termux-package.
Anyone help check it?
Beta Was this translation helpful? Give feedback.
All reactions