docker build fails with ApplyLayer exit no space left on device #50403
Replies: 2 comments 2 replies
-
Hi 👋 For codespaces, we cache a set of images which takes up some space during creation. However, you could get around this by adding an Example - Some other alternatives if you'd like to avoid adding
|
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm trying to get a codespace up for our open source "sirf-exercises" project ,see https://github.com/SyneRBI/SIRF-Exercises/tree/devcontainer/.devcontainer with a
Dockerfile
that essentially just pullssynerbi/sirf:devel
. This is a fairly big image.During codespace creation I get the error
(Full log is available at SyneRBI/SIRF-Exercises#200).
I don't think this is a quota error (I haven't done anything at all with codespaces really, so should have the 32GB available).
Reading on the internet, I see other people reporting the same error with pulling/building large docker images, with a recommendation to switch the docker storage-driver to
overlay2
. I don't know if this could help, or indeed if it's already running this storage-driver, but in any case have no idea how to configure the codespace accordingly.Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions