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

Computer storage filling up with System Data from thousands of "electrons" in Host directory #7428

Open
mx-ruthie opened this issue Sep 23, 2024 · 3 comments

Comments

@mx-ruthie
Copy link

Description

Got notification that the system data on my computer was full:
storage on new computer nearly full
Tracked it down using DaisyDisk:
DaisyDisk scan

The Host folder was hoarding 15,000+ "electrons" that I had to manually delete after all pruning activities failed.
host file full of thousands of electrons

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

Server: Docker Desktop 4.34.2 (167172)
 Engine:
  Version:          27.2.0
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.21.13
  Git commit:       3ab5c7d
  Built:            Tue Aug 27 14:15:41 2024
  OS/Arch:          linux/arm64
  Experimental:     false

docker info

Client:
 Version:    27.2.0
 Context:    desktop-linux
 Debug Mode: false
Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.2-desktop.1
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.2-desktop.2
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.13.0
    Path:     /Users/ruthieirvin/.docker/cli-plugins/docker-scout

Server:
 Containers: 6
  Running: 6

Diagnostics ID

A48EDB00-A3D9-439D-A98A-A3AE25495F9C/20240923184758

Additional Info

Happy to cooperate however.

@mark-dr
Copy link

mark-dr commented Sep 24, 2024

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.

@nivhanin
Copy link

same issue persist on my M1 Pro: 4.34.2 (167172)
My Mac filled with 685 Gigs of logs.
Screenshot 2024-09-26 at 15 04 21
at least 3 files (size: 21MB) of electron.log every minute

image

@mark-dr
Copy link

mark-dr commented Oct 1, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants