kubernetes-sigs/bom

bom will leave cloned modules in tmp

puerco opened this issue · 4 comments

puerco commented

What happened:

To generate license and other data, bom clones the go modules it needs to tmp. It is supposed to remove them after it's done. After trying to generate an SBOM for cilium/cilium, my tmp dir was left with 11 GB of files in /tmp/spdx/gomod-scanner/.

What you expected to happen:

Disk space should be reclaimed after generating the SBOM.

How to reproduce it (as minimally and precisely as possible):

Generate an SBOM and check /tmp/spdx/gomod-scanner/

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale