Closed ktzsolt closed 1 year ago
On the DDEV test runners I'm having to clean up 150-300GB of C:\Users\Testbot\AppData\Local\Temp\docker-scout. Please improve the hygiene here.
And of course... Did I ask for Docker Scout to be doing anything?
This problem is VERY annoying. Please, make the whole Scout or the temp files of the Scout fully optional in Docker Desktop on Windows!
Please try disabling the SBOM background indexer under Settings > Features in development > Experimental features > Enable background SBOM indexing
Please try disabling the SBOM background indexer under
Settings > Features in development > Experimental features > Enable background SBOM indexing
It is disabled for me, also Access experimental features
is disabled but scout still does it's job when opening image and filling up %localappdata%\Temp\docker-scout\
directory with the images as tar files
With the current version 4.25.0 (126437)
this is solved. There is a start scan button now that will start the creation of the tar in %localappdata%\Temp\docker-scout\
and after it is sent to scout the tar is deleted. Thank you!
Description
Even when the "Experimental features" flag is turned off in the settings docker scout is still scanning images when I "open" one of the images in the images menu.
I wouldn't mind this, but scout is filling up the space in
%localappdata%\Temp\docker-scout\
directory, making a tar of all the images that are being scanned and leaving it just there. That can potentially mean tens of gigabytes in a matter of few hours. or less, filling up the C:\ drive.Reproduce
%localappdata%\Temp\docker-scout\
directoryExpected behavior
docker scout should delete the tar in
%localappdata%\Temp\docker-scout\
immediately after it is being sent to the web service for scan.docker version
docker info
Diagnostics ID
7BC791B4-C209-493E-A4B3-7E60DB0ED42A/20230918082442
Additional Info
No response