Is BinaryBuilder supposed to work on Windows?

Made my first try but didn’t go very far (not to mention that it didn’t accept the source location from local disk)

You have the following contents in your working directory:
  - imgtexture

IOError: could not spawn `docker inspect --type=image julia_binarybuilder_rootfs:v2021.7.13-545434`: no such file or directory (ENOENT)

and I have no - imgtexture in my working directory

Short answer is: no, BinaryBuilder.jl doesn’t run on Windows at the moment.

Long answer is: I don’t think there is a reason why it shouldn’t work in principle in the same way it works on macOS (through Docker), but there were some issues that never got addressed because as a matter of fact no one regularly using (let alone developing) BinaryBuilder.jl uses Windows:

I guess it should work if you run Julia in a Linux Docker container.

If you have access to GitHub Codespaces, you can run BinaryBuilder in Yggdrasil in your browser, whatever operating system you use: Home · BinaryBuilder.jl.


Ok, thanks. I subscribed the Codespaces beta. Let’s see how long they take to respond.

What should also work is install WSL, Docker, VS Code and the Remote Container extension. If you then open the Yggdrasil folder in VS Code, it should offer to provision the same env you would get on Codespaces locally on your machine.


A little discussed imbalance: 45% of users use Windows, but most developers use Linux or MacOS.

BinaryBuilder is a tool that is used often one-off. I guess that what happens is that if one finds that it doesn’t run natively on Windows they just skip it: the time to look into fixing it would be larger than the time spent into using it, for most users. So in the end there is probably a a bias selection

1 Like