# No space left on device

**URL:** <https://discuss.circleci.com/t/no-space-left-on-device/3068>\
**Category:** Build Environment\
**Tags:** docker\
**Created:** [April 1, 2016, 6:55am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068 "2016-04-01T06:55:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sigfrid](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sigfrid](https://discuss.circleci.com/u/sigfrid)\
**Post date:** [April 1, 2016, 6:55am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068/1 "2016-04-01T06:55:50Z")

</div>

Hello everyone.  
As part of my build, I’d like to make sure the Dockerfile contains all the instructions to successfully build the image. To do so after running my specs I build the image.

```
- bundle exec rspec spec/
- docker build -t app-image . 

```

The image is about 300 Mb and now when I run my build I get

`ERROR: Failed to create usr/lib/gcc/x86_64-alpine-linux-musl/5.3.0/plugin/include/splay-tree.h: No space left on device`

Are there any constraints on my VM?  
Is there a way to start always with a clean VM? This issue for instance didn’t occur yesterday when the build was basically the same.

Thanks

---

<div class="post-metadata">

**Author:** ![sigfrid](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sigfrid](https://discuss.circleci.com/u/sigfrid)\
**Post date:** [April 1, 2016, 6:58am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068/2 "2016-04-01T06:58:44Z")

</div>

Update.  
I have just rebuilt it and now everything worked fine.  
Am I missing anything here?

Thanks

---

<div class="post-metadata">

**Author:** ![Eric](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/eric/32/2759_2.png) [@Eric](https://discuss.circleci.com/u/Eric)\
**Post date:** [April 1, 2016, 10:31am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068/3 "2016-04-01T10:31:52Z")

</div>

Just wanted to reply briefly with what I’ve seen. I’m not deeply familiar with docker build, but other customers have reported that the docker build step balloons in disk usage. This [SO post](http://stackoverflow.com/questions/26600769/build-context-for-docker-image-very-large) might be a step towards fixing that?

---

<div class="post-metadata">

**Author:** ![sigfrid](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sigfrid](https://discuss.circleci.com/u/sigfrid)\
**Post date:** [April 18, 2016, 9:44am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068/4 "2016-04-18T09:44:54Z")

</div>

Thanks for your reply.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:38am UTC](https://discuss.circleci.com/t/no-space-left-on-device/3068/5 "2018-06-18T11:38:10Z")

</div>