Grype database or disk is full on large Docker images
When Grype or stereoscope scans a large Docker image through the local socket and fails with database or disk is full or no space left on device, measure the scanner temp path, Grype cache, Docker root dir, and container filesystem before pruning anything.
Copy the Grype disk check before pruning Docker data.
Paste the Grype/stereoscope output, Docker root, temp/cache sizes, or issue link and we reply with the safe first step. The free SafeDisk AI deletion trial is only for unclear delete / confirm / protect decisions such as named volumes, scanner cache, Docker root pressure, or large image layers.
Use this before changing scanner cache or pruning Docker volumes.
Paste this into an issue when a vulnerability scan fails on a large image and the host appears to have free space.
Before deleting Docker data, separate the paths that can report "disk full" during a Grype/stereoscope scan:
docker info -f 'DockerRootDir={{ .DockerRootDir }}'
df -hT
df -h "$(docker info -f '{{ .DockerRootDir }}')" 2>/dev/null
docker system df -v
docker run --rm alpine sh -c 'df -hT /tmp; mount | grep " /tmp" || true'
docker volume ls
docker volume inspect dockhand-grype-db --format '{{ .Mountpoint }}' 2>/dev/null | xargs -r -I{} sudo du -sh "{}" 2>/dev/null
If /tmp or the scanner cache is small, move Grype/stereoscope temp/cache to a larger filesystem. If Docker root is tight, prune rebuildable images/build cache first. Review named volumes before any volume prune because monitoring databases and app state often live there.Common false leads
df -h /can look healthy while Docker root, scanner temp, or a cache volume is the actual limit.- A large image can fail during tar extraction even when the final image size looks acceptable.
- Named volumes with zero reclaimable space can still contain application state; do not use broad volume prune as the first fix.
Turn repeated scanner failures into a cleanup plan
Copy the read-only check first. Request the free SafeDisk AI deletion trial only if the output, app state, or cleanup boundary is still not obvious.
Need a delete / confirm / protect answer for Grype or Docker?
Submit the form first; the Grype output, Docker root details, or issue link can follow. We check whether the free first step is enough before asking for the free SafeDisk AI deletion trial.