-
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
containerd issues [was: Docker hv-sock proxy (vsudd) is not reachable] #1359
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@powareverb: Took some time to get to this issue. The error message means that there was an issue with booting the Linux VM. Unlike many other issues with the same symptom, I looked at, your Linux VM boot up just fine and with good speed too (many users see VMs booting very slowly and then hitting a timeout). However, once the Linux VM get's to userspace, not services are started inside the VM:
This is very odd since all this code is burned into a read-only ISO image so shouldn't change. Could you try the latest edge release (and possibly a newer insider build) Thanks |
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. |
@rn cheers for the update. I pulled the latest edge a while back and it has fixed the issue, unfortunately I don't recall which exact release fixed it. Looking at the log, it may be that the disk space got exhausted?
|
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 is accessible
Actual behavior
Docker fails to start with the error:
Docker hv-sock proxy (vsudd) is not reachable
Information
Diagnostic ID
E6369C92-6346-4C3A-A11C-77EF089735E2/2017-11-26_10-39-05
Host
Windows 10 Pro Insider
17046 pre 171118-1403
Docker
Version 17.11.0-ce-win40 (14328)
Channel: edge
6b31b18
Steps to reproduce the behavior
Further details
This install was working previously, but have run into issues recently. Unsure if caused by update to new insider preview, new version of docker, or other issues. There are a number of other issues with the same error, but seems like this is a pretty generic error (many possible causes) so logging it regardless.
Other possibly related issues:
#271
#592
#606
The text was updated successfully, but these errors were encountered: