From 478f8163e24664aea22fe6bcb1c425fb40acd1bf Mon Sep 17 00:00:00 2001 From: Rolf Neugebauer Date: Fri, 19 Jan 2018 13:04:19 +0000 Subject: [PATCH] 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 --- docs/platform-hyperkit.md | 2 +- examples/{vsudd.yml => vsudd-containerd.yml} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename examples/{vsudd.yml => vsudd-containerd.yml} (100%) diff --git a/docs/platform-hyperkit.md b/docs/platform-hyperkit.md index b24ae617a..97f22c0f0 100644 --- a/docs/platform-hyperkit.md +++ b/docs/platform-hyperkit.md @@ -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 sockets on the host, enabling access to other daemons, like `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 -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`. diff --git a/examples/vsudd.yml b/examples/vsudd-containerd.yml similarity index 100% rename from examples/vsudd.yml rename to examples/vsudd-containerd.yml