You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Can't use the tool to scan due to an error that no space left on the device, even though i have enough space
└─$ grype db update -vvv
[0000] INFO grype version: 0.84.0
[0000] DEBUG config:
log:
quiet: false
level: trace
file: ""
dev:
profile: none
db:
cache-dir: /home/groot/.cache/grype/db
update-url: https://toolbox-data.anchore.io/grype/databases/listing.json
ca-cert: ""
auto-update: true
validate-by-hash-on-start: false
validate-age: true
max-allowed-built-age: 120h0m0s
require-update-check: true
update-available-timeout: 30s
update-download-timeout: 5m0s
max-update-check-frequency: 2h0m0s
[0000] TRACE no max-frequency set for update check
[0000] DEBUG checking for available database updates
[0000] DEBUG found database update candidate: Listing(url=https://grype.anchore.io/databases/vulnerability-db_v5_2024-11-19T01:31:45Z_1731990207.tar.gz)
[0000] DEBUG cannot find existing metadata, using update...
[0000] DEBUG database update available: Listing(url=https://grype.anchore.io/databases/vulnerability-db_v5_2024-11-19T01:31:45Z_1731990207.tar.gz)
[0000] INFO downloading new vulnerability DB
[0004] TRACE worker stopped component=eventloop
[0004] TRACE signal exit component=eventloop
unable to update vulnerability database: unable to update vulnerability database: unable to download db: write /tmp/getter2468548383/archive: no space left on device
What you expected to happen:
Get no error when scanning, How to reproduce it (as minimally and precisely as possible):
grype | tee results / grype > results
@rootlikegroot do you have any details on the volumes on the system?
Is there maybe a /tmp or home volume that is out of space that grype is operating on?
Grype downloads the DB to TMPDIR and then copies the contents over to home. Maybe one of these locations is running out of space before grype can execute?
What happened:
Can't use the tool to scan due to an error that no space left on the device, even though i have enough space
└─$ grype db update -vvv
[0000] INFO grype version: 0.84.0
[0000] DEBUG config:
log:
quiet: false
level: trace
file: ""
dev:
profile: none
db:
cache-dir: /home/groot/.cache/grype/db
update-url: https://toolbox-data.anchore.io/grype/databases/listing.json
ca-cert: ""
auto-update: true
validate-by-hash-on-start: false
validate-age: true
max-allowed-built-age: 120h0m0s
require-update-check: true
update-available-timeout: 30s
update-download-timeout: 5m0s
max-update-check-frequency: 2h0m0s
[0000] TRACE no max-frequency set for update check
[0000] DEBUG checking for available database updates
[0000] DEBUG found database update candidate: Listing(url=https://grype.anchore.io/databases/vulnerability-db_v5_2024-11-19T01:31:45Z_1731990207.tar.gz)
[0000] DEBUG cannot find existing metadata, using update...
[0000] DEBUG database update available: Listing(url=https://grype.anchore.io/databases/vulnerability-db_v5_2024-11-19T01:31:45Z_1731990207.tar.gz)
[0000] INFO downloading new vulnerability DB
[0004] TRACE worker stopped component=eventloop
[0004] TRACE signal exit component=eventloop
unable to update vulnerability database: unable to update vulnerability database: unable to download db: write /tmp/getter2468548383/archive: no space left on device
What you expected to happen:
Get no error when scanning,
How to reproduce it (as minimally and precisely as possible):
grype | tee results / grype > results
Environment:
Output of
grype version
:Application: grype
Version: 0.84.0
BuildDate: 2024-11-05T14:54:52Z
GitCommit: c8d5ffc
GitDescription: v0.84.0
Platform: linux/amd64
GoVersion: go1.23.2
Compiler: gc
Syft Version: v1.16.0
Supported DB Schema: 5
OS (e.g:
cat /etc/os-release
or similar):PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2024.3"
VERSION="2024.3"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"
The text was updated successfully, but these errors were encountered: