From d30ddb101fc88fc18a6c0c8f610ca6c88cdc8177 Mon Sep 17 00:00:00 2001
From: Marcus Tillmanns <marcus.tillmanns@qt.io>
Date: Tue, 9 Jul 2024 06:33:54 +0200
Subject: [PATCH] Docker: Use kill to stop container

Calling "stop" often times takes a while or outright fails to stop
some containers. "kill" is more reliable.

Change-Id: I46a33c8f4e38aa9a71b1f64d74042433f7a90ccc
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
---
 src/plugins/docker/dockerdevice.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/plugins/docker/dockerdevice.cpp b/src/plugins/docker/dockerdevice.cpp
index 27878672e8f..7f7c527f18b 100644
--- a/src/plugins/docker/dockerdevice.cpp
+++ b/src/plugins/docker/dockerdevice.cpp
@@ -767,7 +767,7 @@ void DockerDevicePrivate::stopCurrentContainer()
         fileAccess->reset();
 
     Process proc;
-    proc.setCommand({settings().dockerBinaryPath(), {"container", "stop", m_container}});
+    proc.setCommand({settings().dockerBinaryPath(), {"container", "kill", m_container}});
 
     m_container.clear();