CUDA builds instead of fetching from Flox cache

[user.compactor]

Hi,

I’ve been struggling all day with setting up a Python/JAX/CUDA development environment.
I’m using Nix flakes on WSL2 (Fedora), pinned to nixos-25.05.

To save hours (and precious electrons), I added the new Flox CUDA cache to my Nix config (/etc/nix/nix.conf) as documented here:

Nix, Flox, Nvidia Opening Up CUDA Redistribution on Nix

Just landed back from NixCon, somehow every year is even more beautiful. I know that many of us in the Nix community dreamed of a world where Nix’s virtues of reproducibility, determinism, and portability would extend to CUDA projects. We knew this was possible. We also knew it would require alignment and approval with NVIDIA. The team at Flox has been working with NVIDIA over the past months on an agreement to redistribute CUDA Toolkit packages, in partnership with the NixOS Foundation, Nix …

A quick nix show-config confirms that the cache is active.

Issue:
When I run nix develop .#cuda, Nix does fetch non-CUDA packages (Python, etc.), but it still rebuilds every CUDA-related package locally (cudatoolkit, cudnn, nccl, …).
Nothing is fetched from the Flox cache, which is surprising since cudaPackages.cudatoolkit or cudaPackages.cudnn are quite common and large, so (I assume) they should be cached.

I also tried using the older unofficial CUDA cache (cache.nixos-cuda.org), but the result is the same, everything gets built instead of fetched.

Questions:
Am I missing something in the configuration?
Is there a way to check whether a given derivation is actually available in a specific binary cache?

Any insight would help, compiling CUDA under WSL2 is quite slow…

[user.compactor]

Oh yes makes sense, everythings work now, many thanks!

[ron]

Thanks @TiltedToast ! We should definitely get more formal docs/FAQ pages in. If folks are thoughts let me know!

[juaningan]

I missed some messages in this conversation. Could you point out what finally fixed your problem?

[user.compactor]

I think the answer has been deleted. As far as I remember (it’s been few months ), the solution was to pin the floxpkgs with the unstable branch floxpkgs.url = "github:flox/nixpkgs/unstable";