Skip to content
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

Closed
powareverb opened this issue Nov 25, 2017 · 6 comments
Closed

Comments

@powareverb
Copy link

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

  1. Request start docker
  2. Get the error: Docker hv-sock proxy (vsudd) is not reachable

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

@arthurdn

This comment has been minimized.

@ctmcisco

This comment has been minimized.

@rn rn changed the title Docker hv-sock proxy (vsudd) is not reachable containerd issues [was: Docker hv-sock proxy (vsudd) is not reachable] May 1, 2018
@rn
Copy link
Contributor

rn commented May 1, 2018

@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:

[09:24:01.879][Moby           ][Info   ] [   30.233851] IPVS: Creating netns size=2104 id=7
[09:24:01.903][Moby           ][Info   ] [   30.254515] IPVS: ftp: loaded support on port[0] = 21
[09:24:02.194][Moby           ][Info   ] INFO[0000] starting containerd                           module=containerd revision=d0457b221369fa22fc2facdf73266b67993b3959 version=v1.0.0-beta.0
[09:24:02.249][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
[09:24:02.294][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
[09:24:02.360][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.metadata.v1.bolt  error="write /var/lib/containerd/io.containerd.metadata.v1.bolt/meta.db: no space left on device" module=containerd
[09:24:02.402][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
[09:24:02.458][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.differ.v1.walking  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:02.500][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.553][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.grpc.v1.containers  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:02.595][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.648][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.grpc.v1.content  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:02.690][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.740][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.grpc.v1.diff  error="no plugins registered for io.containerd.differ.v1" module=containerd
[09:24:02.782][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.825][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.866][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
[09:24:02.919][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.grpc.v1.images  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:02.962][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
[09:24:03.015][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.grpc.v1.namespaces  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:03.060][Moby           ][Info   ] INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
[09:24:03.135][Moby           ][Info   ] WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/containerd/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
[09:24:03.183][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
[09:24:03.226][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
[09:24:03.286][Moby           ][Info   ] WARN[0001] failed to load plugin io.containerd.grpc.v1.snapshots  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:03.331][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
[09:24:03.378][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
[09:24:03.433][Moby           ][Info   ] WARN[0001] failed to load plugin io.containerd.runtime.v1.linux  error="no plugins registered for io.containerd.metadata.v1" module=containerd
[09:24:03.478][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
[09:24:03.535][Moby           ][Info   ] WARN[0001] failed to load plugin io.containerd.grpc.v1.tasks  error="no plugins registered for io.containerd.runtime.v1" module=containerd
[09:24:03.579][Moby           ][Info   ] INFO[0001] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
[09:24:03.627][Moby           ][Info   ] INFO[0001] serving...                                    address="/run/containerd/debug.sock" module="containerd/debug"
[09:24:03.679][Moby           ][Info   ] INFO[0001] serving...                                    address="/run/containerd/containerd.sock" module="containerd/grpc"
[09:24:03.711][Moby           ][Info   ] INFO[0001] containerd successfully booted in 1.508091s   module=containerd
[09:24:03.766][Moby           ][Info   ] FATA[0001] listing containers                            error="unknown service containerd.services.containers.v1.Containers: not suppo

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

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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.
/lifecycle stale

@powareverb
Copy link
Author

@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?

[09:24:02.294][Moby ][Info ] INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"... module=containerd type=io.containerd.metadata.v1
[09:24:02.360][Moby ][Info ] WARN[0000] failed to load plugin io.containerd.metadata.v1.bolt error="write /var/lib/containerd/io.containerd.metadata.v1.bolt/meta.db: no space left on device" module=containerd

@docker-robott
Copy link
Collaborator

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

@docker docker locked and limited conversation to collaborators Jun 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants