-
Notifications
You must be signed in to change notification settings - Fork 292
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
1.13.0-rc3-beta32.1 (9324) does not start #316
Comments
Thanks, the compose error message is expected since the Linux VM is not running. It's interesting that the stable version is working. Could you upload a diagnostics, it contains additional information which will allow us to debug this further. |
@rneugeba How I do that? |
In the systray there is a little whale icon. right-click on it and select Diagnose & Feedback. Then "Upload diagnostics". This may take a while, but afterwards there should be a diagnostics ID displayed which will us to retrieve the diagnostics |
@rneugeba sorry for the delay here you go:
|
I'm not entirely sure if there is something wrong with your system. The Linux VM booted and there is a container running. Also the log is from the stable release and not from the beta as the title of the issue suggests |
@rneugeba ohhh I complete misunderstood what you ask me. I will upload the report again when I get into home today |
@rneugeba here you go: Upload a diagnostic is not working either .... Here is the log file content:
Don't know if that helps. |
Thanks. does the Upload Diagnostics not finish and print an ID? |
@rneugeba nope, it doesn't finish |
Hmm. Somewhere in |
@dgageot @simonferquel any idea why the debug logs are not uploaded? There doesn't seem to be an obvious error |
@rneugeba sure, that's all I have found |
@reypm thanks for the log files. I see sometime indication that the app used to work on
It also later failed on
and that is the last in the log. I also see various VMware processes running as well as well as VMware network adapters, which seems to suggest that you also use VMware on the system. Unfortunately, Hyper-V, which is used by Docker for Windows, does not work with VMware running at the same time. Could you try un-installing VMware? |
@rneugeba to be honest I don't know for sure what could be happening, you're right Vmware and Hyper-V doesn't like each other so in order to use Docker I had to disable Vmware which I did. After several tries meaning installing and uninstalling Docker, enabling/disabling Hyper-V I make it to work with the beta version. I will try the latest Beta/RC and see if it's still working. Will let you know later today after I get into home |
Thanks for getting back so quick and looking forward hearing back |
@rneugeba I've installed Docker 1.13 RC34 and it didn't work either. Here is the message I got as soon as I try to start Docker:
A crash report has been uploaded with the diagnostic ID: I have Vmware installed but because I've enabled Hyper-V back I can not uninstall it. I will try to remove both and start from scratch. |
After have both uninstalled and install |
I Faced the same issue with Docker Toolbox on Windows 7. Is any workaround avaliable? |
workaround that works for me in Windows 10: reinstall Docker Toolbox. |
@ekropotin @epineda in the latest upgrades I've run I just open Hyper-V and then reset Docker through the GUI 2 or 3 times, that's enough at least for me, the cause not sure @rneugeba any advice here? |
I also get the exac same error message ( |
@tfritsch-km Docker for Windows does not work on Window10 Home... |
Sorry @rneugeba , I should have mentioned I use Docker Toolbox and not Docker for Windows (I thought that mentioning win10Home was clear enough, my fault). Anyway since I got the exact same error message, I thought that the docker quickstart terminal workaround could help here too (I came to this issue when googling for the error). |
NP, it'd odd though because with toolbox there are no named pipes involved... |
@tfritsch-km if you're using Docker Toolbox, remember to run |
Thank you @friism, using |
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 start properly and container can start up
Actual behavior
docker-compose up -d
from Windows Power Shell it ends with the following output:Information
Below is the content log file for Docker:
Steps to reproduce the behavior
docker-compose
NOTE: I can confirm switching to stable version makes everything to work fine
The text was updated successfully, but these errors were encountered: