Cleaning the nix store: Difference between revisions

From NixOS Wiki
No edit summary
Jalil (talk | contribs)
m Remove unnecessary leading white space from command
 
(One intermediate revision by one other user not shown)
Line 7: Line 7:
Sometimes <code>result</code> files created by an ad-hoc <code>nix-build</code> bind a lot of resources, these can be found by running:
Sometimes <code>result</code> files created by an ad-hoc <code>nix-build</code> bind a lot of resources, these can be found by running:


<syntaxhighlight lang=shell>
<syntaxhighlight lang="shell">
  nix-store --gc --print-roots | egrep -v "^(/nix/var|/run/\w+-system|\{memory|/proc)"
nix-store --gc --print-roots | egrep -v "^(/nix/var|/run/\w+-system|\{memory|/proc)"
</syntaxhighlight>
</syntaxhighlight>


Line 23: Line 23:
* https://github.com/cdepillabout/nix-query-tree-viewer
* https://github.com/cdepillabout/nix-query-tree-viewer
* https://github.com/craigmbooth/nix-visualize
* https://github.com/craigmbooth/nix-visualize
[[Category:nix]]

Latest revision as of 07:22, 7 October 2024

Sometimes your store fills up the disk, but a simple

nix-store --gc

does not seem to clean all that much.

This usually means that you have some old collection roots that keep old versions of nixpkgs around.

Sometimes result files created by an ad-hoc nix-build bind a lot of resources, these can be found by running:

nix-store --gc --print-roots | egrep -v "^(/nix/var|/run/\w+-system|\{memory|/proc)"

Additional Resources about cleaning up the nix-store:

There are multiple tools that can help with discovering gcroots and calculate the disk size: