Docker fails to do a cold start #1075
Assignees
Comments
|
I have exactly the same problem. |
|
@metya Same here - even after a clean install yesterday. Restarting from the Settings page seems to work okay though. Crash report: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-09-08_08-13-45 Same error as op: The log is showing: |
|
I have exactly the same problem again... |
|
log is |
|
Just Because
Fix
|
|
I have the same problem. When I open the docker window and click Reset -> Restart it always works. Is it possible to do an automatic restart or add a restart button inside the crash window to help mitigate this problem? |
|
@sinlov I'm on a corporate laptop that had a full version of Win 10 Pro installed and fully up to date (it also means that a reinstall is impossible). I've been having issues with Docker for Windows since I installed but a restart always seems to work now I've reinstalled Hyper-V and Docker for Win. Do you have any other advice please? |
|
Still occurring every day now - @jasonbivins any thoughts on this one? |
|
Same issue here on Windows 10 Pro. Has been happening for more than a month. I just click OK and restart the process (right click on taskbar, close and then start Docker for Windows) which always fixes the issue. Worth noting that I'm using ESET Internet Security (version 10.1.204.0) |
|
For what it's worth, I'm using ESET as well. ESET Nod 32 Antivirus
10.1.219.0
…On Tue, Sep 12, 2017 at 11:44 PM, George ***@***.***> wrote:
Same issue here on Windows 10 Pro. Has been happening for more than a
month. I just click OK and restart the process (right click on taskbar,
close and then start Docker for Windows) which always fixes the issue.
Worth noting that I'm using ESET Internet Security (version 10.1.204.0)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1075 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABS1AWadqKtDC0H1FpXp7rQegX03UN5jks5shvtTgaJpZM4PPhdg>
.
|
|
@BrizzleRocker You can also try excluding the Windows\Temp folder from your AV to see if that's causing the conflict during startup |
|
@jasonbivins thanks for the feedback. No other Hyper VM's on the machine, just Docker. I will Google how to start a new one but I've never used it before! Interestingly it started first time this morning but I've not changed anything on the laptop, massive log file included below for information. Looks like the docker DataBase connection was okay. [08:05:47.383] |
|
@jasonbivins And we're back to failure this morning: Diagnostic ID: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-09-18_08-17-51 Interestingly I tried to build a new Hyper-V machine this morning whilst the docker error was still up (no restart) and got the following: I also tried connecting to the MobyLinuxVM but was unable to. |
|
@jasonbivins just to follow up on the report above, what I hadn't realized at the time was Kaspersky (corporate install) was running a catch-up task. Do you think this had anything to do with it? |
|
@mmisztal1980 How's your docker performing currently? |
|
@jasonbivins Back to timeout errors this week - namely: Diagnostic at: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-09-27_17-24-57 Restart working okay, so there is a workaround currently. |
|
no errors after a recent upgrade |
|
I spoke to soon |
|
Updated to the latest version yesterday, no problems on restarting the laptop three or four times during the course of the day but this morning we're back to the same failure. New diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-10-04_08-09-45 |
This was referenced Oct 4, 2017
|
@jasonbivins Morning buddy - daily error report and a collection for you - Is there anything I can do to help? Similar (if not identical reports): |
|
Hi @BrizzleRocker
|
|
@jasonbivins thanks for the update - I have reinstalled from scratch. Today's learning point is back-up your site databases before uninstalling docker! ;) Reboots seems to be okay so will let you know how it goes on cold start again. Might try tomorrow morning before I go on holiday! |
|
@jasonbivins I've done the from-scratch reinstall, and docker has started successfully. Diagnostic Id |
|
@mmisztal1980 How Can i unistall Hyper-V and the Containers feature in Windows?? I would like to try this procedure but I don't Know How complete these step |
|
@lpignotti search for „turn windows features on or off” in your windows search |
|
@mmisztal1980 @jasonbivins |
|
@jasonbivins so this mornings first boot started fine. Great I thought. I've just started again this afternoon having got back to my office and sure enough failure: Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-10-23_16-46-10 Nothing else changed or updated (to my knowledge) |
|
What annoys me the most is that not only it fails to start, it takes over 10 minutes to fail and only then I can manually restart, and then it's more 10 minutes to start. I can't do anything about it because the "Restart Docker" is disabled while docker is starting. |
|
@jasonbivins A week's holiday has left me feeling refreshed and ready to start again, but sadly Docker still not playing ball. Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-10-30_08-04-07 Related issues update: |
|
I've been having no issues ever since the 're-install all'.
…On Mon, Oct 30, 2017 at 9:10 AM, BrizzleRocker ***@***.***> wrote:
@jasonbivins <https://github.com/jasonbivins> A week's holiday has left
me feeling refreshed and ready to start again, but sadly Docker still not
playing ball.
Docker command did not complete within the allowed timeout. Output:
at Docker.Backend.MobyCommand.RunDocker(String arguments, IDictionary`2 envVariables, String stdin, Int32 timeoutMs, String cidFile) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\MobyCommand.cs:line 152
at Docker.Backend.MobyCommand.Run(String commandLine, IDictionary`2 envVariables, Boolean load, String stdin, Int32 timeoutMs) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\MobyCommand.cs:line 49
at Docker.Backend.SambaShare.MountInMoby(String mount, String drive, Credential cred, CredentialInfo credInfo, String options, String ip) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:line 197
at Docker.Backend.SambaShare.MountInMoby(String drive, Credential credential, Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:line 168
at Docker.Backend.SambaShare.Mount(String drive, Credential credential, Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\SambaShare.cs:line 65
at Docker.Backend.BackendServer.<Run>b__6_10(Object[] args) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\BackendServer.cs:line 52
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145
Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-10-30_08-04-07
Related issues update:
#1260 <#1260>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1075 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABS1AZaK9wcKJv28_363cmiHpkNtPLQLks5sxYR9gaJpZM4PPhdg>
.
|
|
@jasonbivins So another day, a different location and the same crash.
Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-02_08-20-43 Log file: @jasonbivins Sorry if I'm repeating myself. I'm seeing lots of users with very similar issues and appreciate that you're busy and every install is slightly different but it would be re-assuring if I could have some feedback please? Edit: normally a restart is fine but I've just seen the following error having tried it just now: New diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-02_08-35-04 |
|
Trying a reinstall. |
|
I tried a re-install (Hyper-V AND Docker) and all that got me was all my images gone. The problem persists. Could this be related to Active Directory/Group Policy somehow? I am NOT an Administrator on any of my machines, but this seems to only happen on the Windows Domain member PC. YMMV. |
|
So I've reinstalled and for now have chosen not to start Docker on boot. I will be disappointed if this is the workaround but my project is starting and I've run out of time to sort this issue. Update 15 mins after starting my PC @jasonbivins this is now failing when I start for the first time, not on boot. Error is the same Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-03_08-13-49 |
|
So I've set it for Docker to not start on boot in the hope that any conflicting processes will be out of the way by the time I do need to use it but unfortunately I'm still getting this error and then have to do a restart to get it working. @jasonbivins any update on this please? I've reinstalled several times now and although I'm happy to do so again I'm getting a little frustrated with downloading all my images and restoring databases.
Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-07_10-56-10 |
|
@jasonbivins Another day, another failed start identical to the message above. New diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-15_10-19-29 |
|
Well this is curious: This morning I started up a task that runs a docker container shortly after I logged in to Windows. The container started just fine, but then a couple minutes later I got the Docker startup error dialog. But my container was still running. So maybe this is just an issue with monitoring the docker service? Of course, to clear the docker error I used the docker UI to restart which exited my running container. |
|
@jasonbivins back once again... Diagnostic: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-11-21_09-42-45 |
|
+1000 0EDEA2D4-8A07-468B-88B3-DABFE7606ACA/2017-12-06_10-00-53 |
|
@jasonbivins Same problems still occurring - do you have any updates on this please as the team are entering development phase and I need this working consistently to give them confidence. New diag: 2383EC5B-5EC8-432B-97AA-EBDA26D31193/2017-12-07_09-01-51 |
|
After encountering file permission issues (cannot simulate a web server on a hosted environment without changing core code) and this stability issue we are abandoning Docker for Windows and dual booting to linux. Thanks for all your help. |
|
The original posts had issues with the connecting to the database which is no longer used for both version for DfW. Closing this issue |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected behavior
Docker starts normally
Actual behavior
In 99% of cases I'm getting the following exception:
Information
Diagnostic Id 5239E3DB-D0D2-47AE-B158-5D03C5A0619A/2017-09-07_11-12-37
The text was updated successfully, but these errors were encountered: