-
Notifications
You must be signed in to change notification settings - Fork 285
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.
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
Docker keeps crashing at Windows logon / startup #3053
Comments
Might be a duplicate of #1348. |
Thank you for the prompt reply.
I looked at the referenced case but, even though there seems to consensus on the cause, there is no reliable workaround or solution. The only workaround is not secure and I'm in a work / production environment.
If there are any suggestions you may have, please share them so I can make an attempt at fixing this. At this point, I have to wait until Docker crashes so I can restart it and have it work again. Maybe that is a clue? I don't get the error again after restarting Docker from the right-click menu and the whale icon stays white instead of going red.
Let me know if you find anything.
Thank you.
Lorenzo Irizarry
Tech Wizard, IT Ninja, and Game Master Craftsman
…________________________________
From: ngie-eign <notifications@github.com>
Sent: Friday, December 7, 2018 7:22 PM
To: docker/for-win
Cc: Janusd7; Author
Subject: Re: [docker/for-win] Docker keeps crashing at Windows logon / startup (#3053)
Might be a duplicate of #1348<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdocker%2Ffor-win%2Fissues%2F1348&data=02%7C01%7C%7Cef7c01ddc6c944a335e408d65c795325%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636798073480131677&sdata=JGcszjzbC5%2BbHmk3OFLPOw8fDUT6BXQHpAPmBwBKZ9I%3D&reserved=0>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdocker%2Ffor-win%2Fissues%2F3053%23issuecomment-445337984&data=02%7C01%7C%7Cef7c01ddc6c944a335e408d65c795325%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636798073480131677&sdata=mD%2FedGZXgSowyRUigKaodIpumefkNCJZmQyqSZO3uH8%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAjAjYxfiwiigBytGHfjzE_w2v4CXqVx8ks5u2r_wgaJpZM4ZI3NY&data=02%7C01%7C%7Cef7c01ddc6c944a335e408d65c795325%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636798073480131677&sdata=GRvMI94hCPI3RLz3Pj%2FKQceeKva7o2461cYF4Qqsgl8%3D&reserved=0>.
|
Docker 2.0.0.2 on my Windows 10 Enterprise 1809 with LanguageMode = FullLanguage I am also receiving this exact same message. Diagnostic ID: 8BD7572F-8266-43E1-8B48-EB17CAF5C2FD/20190210153838 |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Facing the same issue. Is there any work around? |
Mee to... all the time ...
Expected behaviorActual behaviorInformation
Steps to reproduce the behavior
|
this solved it for me and a coworker: #1221 (comment) |
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Docker starts and initializes normally when Windows starts.
Actual behavior
Docker doesn't start properly and displays the following error message:
Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Hyper-V encountered an error trying to access an object on computer 'EIS-LIRIZARRY-D' because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management service on the computer is running.
at New-Switch, : line 121
at , : line 411
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 92
at Docker.Actions.<>c__DisplayClass19_0.b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 74
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59
Information
Windows Version: 10 Enterprise build 17763 (has been updated since the problem began)
Docker for Windows Version: 2.0 build 4271b9e
Is it reproducible? Yes. Happens every time I log into Windows (even after restarts and re-installation)
NOTE: Restarting Docker from the right-click menu on the task bar icon seems to allow Docker to
initialize properly.
Is the problem new? Yes. Started a few weeks back.
Did the problem appear with an update? Not sure, but highly likely.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: