Closed annemarte closed 5 years ago
wirdehall
commented
5 years ago I have the exact same issue, returned from vacation today and started to work, at lunch time I decided to run the update to 2.1.0.0. And since then I havn't been able to start Docker for windows. I tried rebooting the program as administrator and restarting windows multiple times. I even tried to uninstall and reinstall docker but no dice.
Diagnostic id: 75F5AD22-9438-43DD-9DD2-08062B7B3D18/20190805121116
annemarte
commented
5 years ago Seems there's a corporate policy that is stopping unsigned powershell scripts to run. They have to add it to a policy which make take a while.
wirdehall
commented
5 years ago Thank you @annemarte, I have no reverted to the old version of Docker for windows until this can be resolved.
WayneHiller
commented
5 years ago I am having the same issue with a different error.
System.NullReferenceException: Object reference not set to an instance of an object.
at Docker.ApiServices.ClientConfig.DockerLoginSync.CredentialChanged(String registryUrl, Credential cred)
at Docker.ApiServices.Registries.DockerHub.
RundaScath
commented
5 years ago I too am getting an error at startup for windows 10, but i cannot make heads or tail of the error being produced
2019-08-05T15:36:57Z docker + STORAGE_DRIVER_OPTS=
2019-08-05T15:36:57Z docker + jq -e '."storage-driver"' /run/config/docker/daemon.json
2019-08-05T15:36:57Z docker + :
2019-08-05T15:36:57Z docker + sleep 1
2019-08-05T15:36:57Z docker + '[' -d /var/lib/docker/aufs ]
2019-08-05T15:36:57Z docker + '[' -f /run/config/docker/redirect-logs ]
2019-08-05T15:36:57Z docker + /usr/local/bin/dockerd -H unix:///var/run/docker.sock --config-file /run/config/docker/daemon.json '--swarm-default-advertise-addr=eth0' --userland-proxy-path /usr/bin/vpnkit-expose-port
2019-08-05T15:36:58Z docker unable to configure the Docker daemon with file /run/config/docker/daemon.json: the following directives don't match any configuration option: disable-legacy-registry
2019-08-05T15:36:58Z docker + failed_to_start
2019-08-05T15:36:58Z docker + tail /var/log/docker.log
at Docker.Core.Pipe.NamedPipeClient.
leifan78
commented
5 years ago Same issue here:
Unable to create
at Docker.Core.Pipe.NamedPipeClient.
plantusd
commented
5 years ago The same issue
mikeparker
commented
5 years ago Duplicate of https://github.com/docker/for-win/issues/4376 This is fixed and will be released shortly.
mikeparker
commented
5 years ago Docker Desktop 2.1.0.1 stable has been released with a fix for this now.
WayneHiller
commented
5 years ago After updating Docker now tries to start and then terminates. This error is in the event log.
Application: Docker Desktop.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Docker.WPF.DaemonSettings..ctor(Docker.ApiServices.Actions.IActions, Docker.Core.Mediator`1
Exception Info: System.Reflection.TargetInvocationException at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) at System.Reflection.RuntimeConstructorInfo.Invoke(System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo) at Docker.Core.Di.Singletons.NewInstance(System.Type, Int32)
Exception Info: System.ArgumentException at Docker.Core.Di.Singletons.NewInstance(System.Type, Int32) at Docker.Core.Di.Singletons.Get(System.Type, Int32) at Docker.Core.Di.Singletons.Get[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]() at Docker.WPF.SettingsWindow.InstallPanes(Docker.Core.ContainerEngineMode) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.BroadcastEventHelper.BroadcastEvent(System.Windows.DependencyObject, System.Windows.RoutedEvent) at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(System.Object) at MS.Internal.LoadedOrUnloadedOperation.DoWork() at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
HaimRozen
commented
5 years ago Same issue on version: 2.1.0.1 (37199) Exception I get on startup: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
** Exception Text **
System.NullReferenceException: Object reference not set to an instance of an object.
at Docker.ApiServices.ClientConfig.DockerLoginSync.CredentialChanged(String registryUrl, Credential cred)
at Docker.ApiServices.Registries.DockerHub.
** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
WayneHiller
commented
5 years ago After updating to 2.1.0.1, I had to uninstall and the reinstall. All good now.
docker-robott
commented
4 years ago 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
Error message: "Unable to stop ved Docker.Core.Pipe.NamedPipeClient.d5.MoveNext()
--- Slutt på stakksporing fra forrige plassering der unntak ble iverksatt ---
ved System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
ved Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters)
ved Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup)
ved Docker.Actions.<>cDisplayClass24_0.b0()
ved Docker.ApiServices.TaskQueuing.TaskQueue.<>cDisplayClass17_0.<.ctor>b__1()
"
Expected behavior
Docker to start
Actual behavior
Doesn't start
Information
After changing memory settings on older version, and getting an error, I updated to the newest version. I've tried reset to factory defaults several times.
Steps to reproduce the behavior