Repository navigation
Courgette.log file created on the desktop #12468
Description
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID:
Actual behavior
Docker Desktop creates a file called courgette.log on the desktop every time it upgrades.
Expected behavior
The log file should not be created on the desktop.
Information
- Windows Version: Windows 11 Home, 22000.376
- Docker Desktop Version: 4.3.2
- WSL2 or Hyper-V backend? WSL2
- Are you running inside a virtualized Windows e.g. on a cloud server or a VM:
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Steps to reproduce the behavior
- ...
- ...
Reacted by Kevin Schoenfeld, Omniwot, Bill Menees, Brian Hagerty, Vladimir Malzam, Rickard Bemm, helgasoft, Micah Resnick, Florian Depraz, Christos Koutsouradis and 21 more
Activity
SebastienPittet commentedon Dec 28, 2021
Same here!
[362:16:17:16.622][I] ipc.NewClient: 17c2e309-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service.exe
[goroutine 1 [running, locked to thread]:
[win/backend/pkg/service.NewClientForPath(...)
[ win/backend/pkg/service/service.go:26
[win/backend/pkg/service.NewClient(...)
[ win/backend/pkg/service/service.go:20
[common/pkg/diagkit/gather/diagnose.init()
[ common/pkg/diagkit/gather/diagnose/ipc_windows.go:23 +0x13b
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
No fatal errors detected.
fourofspades commentedon Dec 31, 2021
Been trying to work out what the hell has been doing this for a long time. Concerned about low level trojans and all sorts of other nasties.
Thanks Docker for wasting my time. Clearly your "engineers" have never heard of %temp%
deltaepsilon commentedon Jan 28, 2022
So glad this isn't just me.
Omniwot commentedon Feb 11, 2022
Same issue here
bhagerty commentedon Feb 17, 2022
Thanks for opening this issue! What a silly bug!
baterflyrity commentedon Feb 19, 2022
Having this bug since the origin. Recent February update still bring new empty courgette.log file.
PascalMagnard commentedon Mar 3, 2022
Same here, courgette.log on Windows 10 desktop after each Docker upgrade.
fhdalikhan commentedon Mar 24, 2022
Just had this same file created on windows 11
aschkenasy commentedon Mar 25, 2022
just happened to me although it created it only in the running containers root
SalehEssamSaleh commentedon Apr 20, 2022
Same here!
so I should remove it or what should I do!
and there is any way to make Docker liter!
Because my laptop i3 second-generation 6GB RAM and 500 GB HHD
which is already super old and I need to use Docker for studying purposes.
So any ideas and thank you a lot.
guydumais commentedon Apr 22, 2022
Same here:
Docker Desktop 4.7.1 (77678)
Windows 11
KoNyan2612 commentedon May 20, 2022
Same here:
Docker Desktop 4.8.2 (79419)
Windows 11
Xtr102 commentedon Jun 28, 2022
Same issue here. Though it only created it in the running container root.
SubaruSama commentedon Jul 2, 2022
Possible related: https://chromium.googlesource.com/chromium/src/+/32352ad08ee673a4d43e8593ce988b224f6482d3/courgette/courgette_tool.cc#434
In some part of the code or during the update, it launches some chromium. Any Engineer from Docker can confirm this?
drewbritton commentedon Sep 19, 2022
It's comforting to know that this is just a harmless side effect of applying Docker desktop updates. But I have to admit I still find the totally empty courgette.log file appearing on my desktop a bit ominous...
solarpolar commentedon Oct 5, 2022
Still happening - and must send this issue on github a heap of traffic!
elvaret commentedon Oct 8, 2022
me too
linghengqian commentedon Oct 28, 2022
courgetteisGoogle's differential algorithm inChrome/Chromium, which is used for incremental updates to theChromebrowser. But I still don't understand why this problem persists, as it persists inDocker Desktop 4.13.0 (89412).Jens-G commentedon Dec 1, 2022
Still happening.
File is created by some courgette64.exe (located in Docker program folder) and that looks indeed pretty much like
julbra commentedon Feb 1, 2023
It's 2023 and we still get this empty courgette.log haunting millions of desktops after every single update.
yooakim commentedon Mar 28, 2023
Same issue as everyone else here. Still happening.
baterflyrity commentedon Mar 28, 2023
Seems docker team officially dont give a crap about windows community.
Trystan-SA commentedon Apr 4, 2023
Did I just yelled at my colleagues for this?
changetol8 commentedon Apr 8, 2023
I had the same issue by last update
thaJeztah commentedon Apr 10, 2023
👋 I work at Docker, but not on this part of the code, but I stumbled upon this ticket and checked with the team (asked them to have a look). It looks like they have a fix for this (it's currently being reviewed).
The
courgette.logis indeed part of the "delta updater", and in some cases it may write this file. So the good news is that there should be no reason for concern about the file, but it definitively shouldn't end up on your Desktop 😅 (more so, because the filename is rather "weird" and because of that, difficult to associate with "Docker Desktop").The fix that's being reviewed will disable these logs, and should end up in the next (4.19) release of Docker Desktop.
maxcleme commentedon Apr 27, 2023
Closing this issue because a fix has been released in Docker Desktop 4.19.0. See the release notes for more details.
docker-robot commentedon Jun 23, 2023
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
/lifecycle locked