examples: Rename vsudd.yml to vsudd-containerd.yml

This describes more accurately that the example exposes
containerd to the host.

Also adjust platform-hyperkit.md

Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
This commit is contained in:
Rolf Neugebauer 2018-01-19 13:04:19 +00:00
parent d11fe6ba9a
commit 478f8163e2
2 changed files with 1 additions and 1 deletions

View File

@ -177,7 +177,7 @@ domain socket inside the VM to the host via virtio or Hyper-V sockets.
With HyperKit, the virtio sockets can be exposed as unix domain With HyperKit, the virtio sockets can be exposed as unix domain
sockets on the host, enabling access to other daemons, like sockets on the host, enabling access to other daemons, like
`containerd` and `dockerd`, from the host. An example configuration `containerd` and `dockerd`, from the host. An example configuration
file is available in [examples/vsudd.yml](/examples/vsudd.yml). file is available in [examples/vsudd-containerd.yml](/examples/vsudd-containerd.yml).
After building the example, run it with `linuxkit run hyperkit After building the example, run it with `linuxkit run hyperkit
-vsock-ports 2374 vsudd`. This will create a unix domain socket in the state directory that maps to the `containerd` control socket. The socket is called `guest.00000946`. -vsock-ports 2374 vsudd`. This will create a unix domain socket in the state directory that maps to the `containerd` control socket. The socket is called `guest.00000946`.