Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temp file location/filling up? #153

Closed
sbehrens opened this issue Apr 22, 2016 · 5 comments
Closed

Temp file location/filling up? #153

sbehrens opened this issue Apr 22, 2016 · 5 comments
Labels
kind/cleanup no functional changes, only reorganization

Comments

@sbehrens
Copy link

Hello,

I've noticed when running the 'analyze-local-images' tool a few times that I start running out of disk space (until I reboot the system, restarting the Docker machine or removing the images doesn't help). Where are the temp files located and are they being removed after the analyzer completes?

@rmartinez3
Copy link

The temp files should be located in your /tmp folder. it was for mine. it should be a folder called analyze-lcoal-images or something like that. I had to remove it since it was filling my computer up

@sbehrens
Copy link
Author

Thanks, I just confirmed it's not cleaning up temp files correctly.

sbehrens@lgml-sbehrens3 /var/folders/j7/c6s0xn0x3nj86j5jjhn89fbm4xhv43/T$ ls -l | grep analyze                                                                                                                                              1 ↵
drwx------   7 sbehrens  sbehrens   238 Apr 22 09:42 analyze-local-image-077522631
drwx------   8 sbehrens  sbehrens   272 Apr 22 09:44 analyze-local-image-145196438
drwx------   9 sbehrens  sbehrens   306 Apr 22 09:42 analyze-local-image-191599799
drwx------  41 sbehrens  sbehrens  1394 Apr 22 09:41 analyze-local-image-257114695
drwx------  43 sbehrens  sbehrens  1462 Apr 22 09:18 analyze-local-image-328548829
drwx------  62 sbehrens  sbehrens  2108 Apr 22 08:46 analyze-local-image-395502097
drwx------  13 sbehrens  sbehrens   442 Apr 22 09:48 analyze-local-image-421464594
drwx------  19 sbehrens  sbehrens   646 Apr 22 08:51 analyze-local-image-492539904
drwx------  35 sbehrens  sbehrens  1190 Apr 22 09:08 analyze-local-image-535277259
drwx------  26 sbehrens  sbehrens   884 Apr 22 09:04 analyze-local-image-551364093
drwx------  40 sbehrens  sbehrens  1360 Apr 22 09:25 analyze-local-image-706063211
drwx------   2 sbehrens  sbehrens    68 Apr 22 09:52 analyze-local-image-777429368
drwx------  44 sbehrens  sbehrens  1496 Apr 22 09:33 analyze-local-image-814373925
drwx------   7 sbehrens  sbehrens   238 Apr 22 09:42 analyze-local-image-983906511

@Quentin-M
Copy link
Contributor

Hi,

Thanks for the report.

Which version of the analyze-local-images tool are you using? This issue should have been fixed by 1040dbb. I will investigate that if you are running the latest version.

@Quentin-M Quentin-M added component/contrib kind/cleanup no functional changes, only reorganization labels Apr 22, 2016
@sbehrens
Copy link
Author

Fixed in the later build, thanks.

@Quentin-M
Copy link
Contributor

Quentin-M commented Apr 25, 2016

Awesome! I was actually looking at it and I just noticed that in some cases (i.e. SIGINT), it does not clean properly. Linking #158.

To answer the initial question, this contrib tool uses the TMPDIR environment variable (or /tmp if there's none) and then creates a folder named analyze-local-images-XXX where XXX is a random generated number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup no functional changes, only reorganization
Development

No branches or pull requests

3 participants