finavatar
September 15, 2022, 7:34pm
1
Hi,
Thanks.
rimelek
September 16, 2022, 7:30pm
2
Where did you find that file?
If that is a log text file, you can most likely delete it without causing any damage,
You can also join this conversation on GitHub:
opened 01:22AM - 27 Dec 21 UTC
<!--
************************************************************************… ************
*READ ME FIRST*
This repository is for reporting bugs with the Docker Desktop for Windows software,
which we respond to on a best-effort basis.
Do *not* paste logfiles into github issues: upload diagnostics instead, which are
only visible to Docker engineers.
Support requests in this repository (i.e., trouble installing or using the
software) will be ignored, but personalized support is available to Docker Pro and
Team customers at https://hub.docker.com/support/desktop/, and community support is
available from the Docker community Slack (https://www.docker.com/docker-community).
Issues without sufficient detail to debug them will be closed. They generally need
a clear title and description, steps to reproduce, and a diagnostics ID. See
https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for
how to generate a diagnostics ID either from inside the app or from the command line.
************************************************************************************
-->
- [x] 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
<!--
Please, help us understand the problem. For instance:
- Is it reproducible?
- Is the problem new?
- Did the problem appear with an update?
- A reproducible case if this is a bug, Dockerfiles with reproduction inside is best.
-->
- 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
<!--
A reproducible case, Dockerfiles with reproduction inside is best.
-->
1. ...
2. ...