From f279329456244aae888ddd9772e427f5dafb4dbc Mon Sep 17 00:00:00 2001 From: Rolf Neugebauer Date: Thu, 21 Apr 2016 13:54:05 +0100 Subject: [PATCH] vsudd: start vsudd on Windows against a GUID Using 23a432c2-537a-4291-bcb5-d62504644739 as the GUID (randomly generated). The Windows host side will uses this as service ID, once written. Signed-off-by: Rolf Neugebauer --- alpine/packages/vsudd/etc/init.d/vsudd | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/alpine/packages/vsudd/etc/init.d/vsudd b/alpine/packages/vsudd/etc/init.d/vsudd index ee787ab69..686fc030c 100755 --- a/alpine/packages/vsudd/etc/init.d/vsudd +++ b/alpine/packages/vsudd/etc/init.d/vsudd @@ -11,6 +11,12 @@ start() { ebegin "Starting docker socket vsock passthrough" + if [ -d /sys/bus/vmbus ]; then + PORT=23a432c2-537a-4291-bcb5-d62504644739 + else + PORT=2376 + fi + [ -n "${PIDFILE}" ] || PIDFILE=/var/run/vsudd.pid [ -n "${LOGFILE}" ] || LOGFILE=/var/log/vsudd.log @@ -19,7 +25,7 @@ start() --exec /sbin/vsudd \ --make-pidfile --pidfile ${PIDFILE} \ --stderr "${LOGFILE}" --stdout "${LOGFILE}" \ - -- -port 2376 -sock /var/run/docker.sock + -- -port "${PORT}" -sock /var/run/docker.sock eend $? "Failed to start vsudd" }