From 2dca1bc6337043e25e626b4444da29b3ca5d3660 Mon Sep 17 00:00:00 2001 From: John Howard Date: Mon, 12 Oct 2015 14:32:59 -0700 Subject: [PATCH] Windows: Enable kill (part one) Signed-off-by: John Howard --- pkg/signal/signal_unsupported.go | 2 +- pkg/signal/signal_windows.go | 11 +++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/pkg/signal/signal_unsupported.go b/pkg/signal/signal_unsupported.go index cefb2407b6..161ba27397 100644 --- a/pkg/signal/signal_unsupported.go +++ b/pkg/signal/signal_unsupported.go @@ -1,4 +1,4 @@ -// +build !linux,!darwin,!freebsd +// +build !linux,!darwin,!freebsd,!windows package signal diff --git a/pkg/signal/signal_windows.go b/pkg/signal/signal_windows.go index b0585b0ed9..c80a951c50 100644 --- a/pkg/signal/signal_windows.go +++ b/pkg/signal/signal_windows.go @@ -14,3 +14,14 @@ const ( // DefaultStopSignal is the syscall signal used to stop a container in windows systems. DefaultStopSignal = "15" ) + +// SignalMap is a map of "supported" signals. As per the comment in GOLang's +// ztypes_windows.go: "More invented values for signals". Windows doesn't +// really support signals in any way, shape or form that Unix does. +// +// We have these so that docker kill can be used to gracefully (TERM) and +// forcibly (KILL) terminate a container on Windows. +var SignalMap = map[string]syscall.Signal{ + "KILL": syscall.SIGKILL, + "TERM": syscall.SIGTERM, +}