Closed mx-ruthie closed 3 weeks ago
Thanks for raising this, and sorry for the pain it's causing. We've identified the likely cause and we've got a patch into 4.35 (released this week). We think that'll fix it, but we're also tightening up our logging code as extra protection against this sort of over-logging, and hopefully we'll get that into this week's release as well. Please let us know if this persists in 4.35 and I'll make it my top priority to fix it.
same issue persist on my M1 Pro: 4.34.2 (167172) My Mac filled with 685 Gigs of logs. at least 3 files (size: 21MB) of electron.log every minute
Quick update: We've hit some delays on releasing 4.35, so we're planning to release a 4.34.3 version (likely this week) that addresses this issue.
Has this been released yet?
@mx-ruthie, @nivhanin, @adambirds: Sorry for the delay, but I'm happy to let you know that 4.34.3 released today! It'll be offered to you in the app as it's rolled out to users, or you can jump the queue and grab an installer - see release notes and download links here.
The new version should immediately clear up your log files when you run it and then keep them at a reasonable level. Please reach out here if you see any issues and I'll jump straight on it.
@mx-ruthie, @nivhanin, @adambirds: Sorry for the delay, but I'm happy to let you know that 4.34.3 released today! It'll be offered to you in the app as it's rolled out to users, or you can jump the queue and grab an installer - see release notes and download links here.
The new version should immediately clear up your log files when you run it and then keep them at a reasonable level. Please reach out here if you see any issues and I'll jump straight on it.
Seems to be better so far. Not sure on the auto clear as I removed them all in the CLI, but seems better since the update and will check again tomorrow.
@mark-dr this appears to have fixed it, a day later and no large logs files any more. Not sure if you want to update the corresponding issues for windows too:
Hi @mark-dr,
Thanks for the prompt fix!
I wasn't even aware this was an issue for me until my coworkers pointed me to this thread and I discovered I do in fact have a ton of very large logs in ~/Library/Containers/com.docker.docker/Data/log/host
.
I recently updated to Docker Desktop for Mac version 4.34.3 (170107). It appears that the electron log files are now generated at a reasonable rate and size; however they were not automatically cleared as you mentioned they should.
In this screenshot of the output of ls- l
, you can see the size of the logs drop from ~20MB generated every minute to a few KB every hour or so around Oct 21 when I updated.
I'm personally fine deleting these myself but I'm worried other users who didn't know they had this issue would know that they need to go delete stuff. Please let me know if there's any info I can provide that might help debug the auto clear!
Heya @cewkrupa, thanks for the info! I just checked and yep, sorry, it looks like I misspoke - the fix for creation of the log files is in 4.34.3, but the deletion of old ones got bumped to 4.35 (we try to reserve patch releases for particularly critical fixes, and at the time 4.35 was due to be released just a week or so later). 4.35 hit some delays, but we've worked through most (all? 🤞) of them, so I'm hopeful it'll land soon.
@cewkrupa: FYI v4.35.0 was released today. I appreciate you've probably manually cleaned up by now, but if not, the new version should do it for you 🙂
Closing as fixed (excessive logging fixed in v4.34.3, automatic cleanup in v4.35.0). As always, please let us know if it doesn't work for you or if you see regressions. Thanks for your patience with this issue, everyone 🙂
Description
Got notification that the system data on my computer was full: Tracked it down using DaisyDisk:
The Host folder was hoarding 15,000+ "electrons" that I had to manually delete after all pruning activities failed.
Several other people at my company are also experiencing this one after the other and we're circulating the fix we tracked down to dump all the files out of the Host directory manually.
Reproduce
Not sure how to reproduce but hopefully the screenshots of the issue will help.
Expected behavior
I would expect Docker not to maybe infinitely look the same error?
docker version
docker info
Diagnostics ID
A48EDB00-A3D9-439D-A98A-A3AE25495F9C/20240923184758
Additional Info
Happy to cooperate however.