-
Notifications
You must be signed in to change notification settings - Fork 303
Description
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID: FDE0ABED-6F2B-4CE9-8A81-076F8762BD51/20210913131509
Actual behavior
After my mahcine a restarted docker desktop doesn't start:
"Docker failed to initialize"
System.NullReferenceException:
Object reference not set to an instance of an object.
at Docker.Systray.Systray.ExitThreadCore() in C:\workspaces\PR-16319\src\github.com\docker\pinata\win\src\Docker.Desktop\Systray\Systray.cs:line 281
at System.Windows.Forms.Application.ThreadContext.ExitCommon(Boolean disposing)
at System.Windows.Forms.Application.ExitInternal()
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Control.WndProcException(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Docker.Program.Run(IReadOnlyCollection`1 args) in C:\workspaces\PR-16319\src\github.com\docker\pinata\win\src\Docker.Desktop\Program.cs:line 295
Expected behavior
docker starts without issue
Information
-
Is it reproducible?
Restarting again doesn't fix the issue. I have to uninstall and re-install for docker desktop to work. If I then restart it is broken and I'm back to reinstalling -
Is the problem new?
since upgrading to windows 11 I've experienced this. -
Did the problem appear with an update?
not sure -
Windows Version: 11
-
Docker Desktop Version: 4.0
-
WSL2 or Hyper-V backend? WSL2
Steps to reproduce the behavior
- Install docker desktop
- Restart the machine
- Try and launch docker desktop

