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.

Sign up for GitHub

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

Jump to bottom

Docker duplicates the complete Application Event Log#6258

Closed
1 of 2 tasks
Hickstone opened this issue Apr 7, 2020 · 5 comments
Closed
1 of 2 tasks

Docker duplicates the complete Application Event Log #6258

Hickstone opened this issue Apr 7, 2020 · 5 comments
Labels
lifecycle/locked status/acknowledged version/2.2.0.5

Comments

@Hickstone
Copy link

  • I have tried with the latest version of my channel (Stable)
  • I have uploaded Diagnostics (I won't upload as it may contain sensitive data)

Expected behavior

The Files %LOCALAPPDATA%\Docker\log.txt and %PROGRAMDATA%\DockerDesktop\service.txt contain only docker relevant information.

Actual behavior

The logs contain ALL log entries from the Windows Application Event Log.
The files will also contain the same content, but I think that may be to enable multi user diagnostics. (I'm the only docker user on my computer)

Information

  • Is it reproducible? Yes.
  • Is the problem new? Don't know. I found it while searching for another problem.
  • Did the problem appear with an update? Same as above
  • Windows Version: Windows 10 Enterprise 1809 (17763.1039)
  • Docker Desktop Version: 2.2.0.5
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No.

Steps to reproduce the behavior

Start Powershell with Admin rights and type the following:

# Only if the source "foobar" doesn't exist
[System.Diagnostics.Eventlog]::CreateEventSource("foobar", "Application")
Write-EventLog -LogName Application -Source foobar -EventID 1234 -Message "Hello FooBar!"

The created log message will appear in the log.txt and service.txt desipite it's relevance to Docker.
@mat007
Copy link
Member

mat007 commented Apr 10, 2020

Thanks for the report.
There must be something else going on, as I can’t reproduce it using the same Docker Desktop version and the PS commands you provided.
🤔

@mat007
Copy link
Member

mat007 commented Apr 10, 2020

Oh I just realized I wasn’t in Windows containers mode…
I can confirm I am able to reproduce the issue, thanks!

@mat007
Copy link
Member

mat007 commented Apr 10, 2020

This has now been fixed and will be available in the next release.
Thanks!

@stephen-turner
Copy link
Contributor

Fixed in 2.3, closing this ticket.

@docker-robott
Copy link
Collaborator

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.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/locked status/acknowledged version/2.2.0.5
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests

4 participants
@mat007 @stephen-turner @Hickstone @docker-robott