# BinaryBuilder sandbox No space left on device

**URL:** <https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499>\
**Category:** Tooling\
**Tags:** binarybuilder\
**Created:** [February 6, 2026, 11:39am UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499 "2026-02-06T11:39:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 6, 2026, 11:39am UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/1 "2026-02-06T11:39:36Z")

</div>

Trying to build a binary with BinaryBuilder fails with “No space left on device”:

```julia-auto
sandbox:${WORKSPACE}/srcdir/Slint.jl/deps/SlintWrapper # df -h
Filesystem Size Used Available Use% Mounted on
overlay 1.0G 1.0G 0 100% /
df: /opt/x86_64-linux-musl/nonce: No such file or directory
df: /opt/x86_64-linux-musl/GCCBootstrap-5.2.0: No such file or directory
df: /opt/x86_64-linux-musl/PlatformSupport-2025.8.13: No such file or directory
df: /opt/x86_64-linux-musl/RustToolchain-1.91.0-x86_64-linux-musl): No such file or directory
df: /opt/x86_64-linux-musl/RustToolchain-1.91.0-x86_64-linux-gnu): No such file or directory
df: /opt/x86_64-linux-musl/RustBase-1.91.0: No such file or directory
df: /opt/x86_64-linux-musl/LLVMBootstrap-18.1.7: No such file or directory
df: /opt/x86_64-linux-gnu/GCCBootstrap-5.2.0: No such file or directory
df: /opt/x86_64-linux-gnu/PlatformSupport-2025.8.13: No such file or directory
overlay 1.0G 1.0G 0 100% /opt/x86_64-linux-gnu
overlay 1.0G 1.0G 0 100% /opt/x86_64-linux-musl
udev 7.8G 0 7.8G 0% /dev/null
udev 7.8G 0 7.8G 0% /dev/tty
udev 7.8G 0 7.8G 0% /dev/urandom
/dev/vda4 384.3G 103.6G 261.1G 28% /etc/resolv.conf
/dev/vda4 384.3G 103.6G 261.1G 28% /opt/toolchains
/dev/vda4 384.3G 103.6G 261.1G 28% /opt/bin
/dev/vda4 384.3G 103.6G 261.1G 28% /meta
/dev/vda4 384.3G 103.6G 261.1G 28% /workspace
overlay 384.3G 103.6G 261.1G 28% /workspace/srcdir

```

What I found, like  
`mount -t tmpfs -o size=12G tmpfs /workspace/srcdir`  
seems not to apply.

What can I do?

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [February 6, 2026, 12:13pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/2 "2026-02-06T12:13:12Z")

</div>

> [@oheil](#):
>
> Trying to build a binary with BinaryBuilder fails with “No space left on device”:

That’s not very specific, is it? What’s the partition where you don’t have more space? For what is worth, `/tmp` is mounted on a tiny 1 GB, that’s easy to fill out, but `/workspace/srcdir` should have access to your entire disk space.

Summary: find what’s writing where, if possible direct it to partitions where you have plenty of space. Temporary directories can be changed by setting the [`TMPDIR`](https://en.wikipedia.org/wiki/TMPDIR) environment variable (that’s a general Unix thing)

> <https://github.com/JuliaPackaging/Yggdrasil/blob/2fab96df306e2cb011ce4bceb7edba361cdc4230/O/OpenModelica/build_tarballs.jl#L16-L19>

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 6, 2026, 12:17pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/3 "2026-02-06T12:17:02Z")

</div>

> [@giordano](#):
>
> That’s not very specific, is it?

I provided the output of `df -h` inside the sandbox. So that’s most specific I can be with my knowledge about this.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [February 6, 2026, 12:17pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/4 "2026-02-06T12:17:50Z")

</div>

You didn’t show the error message, which should hopefully tell you where the file is being attempted to be written to.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 6, 2026, 12:39pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/5 "2026-02-06T12:39:42Z")

</div>

This is the error:

```julia-auto
warning: build failed, waiting for other jobs to finish...
error: failed to write /tmp/rustczDZ2xr/lib.rmeta: No space left on device (os error 28)

error: could not compile `jiff` (lib) due to 1 previous error
error: failed to write /tmp/rustcNcVkJj/lib.rmeta: No space left on device (os error 28)

error: could not compile `i-slint-backend-winit` (lib) due to 1 previous error
error: failed to write /tmp/rustc2qVfV6/lib.rmeta: No space left on device (os error 28)

error: could not compile `slint-interpreter` (lib) due to 1 previous error

```

It is `/tmp`.

So I am going to use `TMPDIR` with `/workspace/srcdir/tmp` and let you know, if this resolves the problem.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 6, 2026, 3:37pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/6 "2026-02-06T15:37:48Z")

</div>

I wasn’t just providing another `/tmp` folder but a folder `/opt/x86_64-linux-musl/registry` which is created during the build and filled up.

Doing

```julia-auto
mkdir opt-x86_64-linux-musl
mkdir opt-x86_64-linux-musl/registry
ln -s /workspace/srcdir/opt-x86_64-linux-musl/registry /opt/x86_64-linux-musl/registry

```

in the sandbox before building made the build successful.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 6, 2026, 5:29pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/7 "2026-02-06T17:29:46Z")

</div>

After hours of hours of waiting for failed builts (like riscv64-linux-gnu, arm-unknown-linux and others) and silent ending except for `WizardState [step5c]` I give this up for now. Only the first build (x86\_64-linux-gnu) worked. Thanks for your help anyways.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [February 6, 2026, 7:40pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/8 "2026-02-06T19:40:21Z")

</div>

If you just search for your error messages on Yggdrasil you should find the answers to your problems, most recent PR which solved all these problems: [[Qiskit] Bump to version 2.3.0 by garrison · Pull Request #12935 · JuliaPackaging/Yggdrasil · GitHub](https://github.com/JuliaPackaging/Yggdrasil/pull/12935).

> [@oheil](#):
>
> After hours of hours of waiting for failed builts (like riscv64-linux-gnu, arm-unknown-linux and others) and silent ending except for `WizardState [step5c]` I give this up for now.

I don’t know how to stress it more than [what it’s already in the documentation](https://docs.binarybuilder.org/stable/#Manually-create-or-edit-build_tarballs.jl), but the wizard isn’t really great if you need to fiddle with a build.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [February 7, 2026, 2:15pm UTC](https://discourse.julialang.org/t/binarybuilder-sandbox-no-space-left-on-device/135499/9 "2026-02-07T14:15:04Z")

</div>

Thanks, especially this part:

> To generate this file (explained in greater detail in [Building Packages](https://docs.binarybuilder.org/stable/building/)), one can clone `Yggdrasil` , copy an existing build recipe, modify it, and submit a new pull request.

gives me new hope. I am still a bit concerned about `copy an existing build recipe`. Sounds easy enough but my guess is, not just copy any recipe, but I would do best to copy a recipe which is similar to my needs (with rust e.g.) and the sheer number of recipes let me doubt my search skills… but anyways, I will give it a try as soon as I have time (somewhere during next week).

Thanks again for your encouragement 🙏🙋‍♂️