fix: workaround podman stop/rm timeout in rootless mode with --pid host

In rootless mode with --pid host (distrobox default), podman stop/rm --force
times out because "crun kill --all" fails when the container's cgroup-path
is empty.

Root cause: When using --pid host, the container shares the host's PID
namespace and crun doesn't create a dedicated cgroup. The "crun kill --all"
command relies on cgroup to find processes, but with empty cgroup-path,
no processes are found and killed.

Solution: Call "podman kill" before stop/rm, which uses "crun kill" (without
--all flag) that sends signals directly to the container's init process PID,
bypassing the cgroup lookup issue.

Fixes: #1939
See also: chimera-linux/cports#1718

Signed-off-by: xz-dev <xiangzhedev@gmail.com>

Author: xz-dev

distrobox-rm

@@ -389,6 +389,28 @@ delete_container()
 
 	# Remove the container
 	printf "Removing container...\n"
+	# Workaround for podman rm --force timeout issue with --pid host in rootless mode.
+	# See: https://github.com/chimera-linux/cports/issues/1718
+	#
+	# Root cause: In rootless mode with --pid host (distrobox default), the container's
+	# cgroup-path is empty. When podman rm --force tries to stop the container, it uses
+	# "crun kill --all" which relies on cgroup to find processes. With empty cgroup-path,
+	# no processes are found and killed, causing the stop to timeout.
+	#
+	# Solution: Use "podman kill" first, which calls "crun kill" (without --all flag).
+	# This sends the signal directly to the container's init process PID, bypassing
+	# the cgroup lookup issue.
+	#
+	# Note: distrobox-rm does not call distrobox-stop (by design, it relies on
+	# "podman rm --force" to handle stopping). A similar fix exists in distrobox-stop
+	# for the "distrobox stop" command.
+	if [ "${container_status}" = "running" ] && [ "${rootful}" -eq 0 ]; then
+		case "${container_manager}" in
+			*podman*)
+				${container_manager} kill "${container_name}" > /dev/null 2>&1 || :
+				;;
+		esac
+	fi
 	# shellcheck disable=SC2086,SC2248
 	${container_manager} rm ${force_flag} --volumes "${container_name}"
 

distrobox-stop

@@ -290,7 +290,20 @@ case "${response}" in
 	y | Y | Yes | yes | YES)
 		# Stop the container
 		for container_name in ${container_name_list}; do
-			${container_manager} stop "${container_name}"
+			# Workaround for podman stop timeout issue with --pid host in rootless mode.
+			# See: https://github.com/chimera-linux/cports/issues/1718
+			# In rootless mode, podman stop uses "crun kill --all" which fails when
+			# cgroup-path is empty (which happens with --pid host, the distrobox default).
+			# Using "kill" first (which uses "crun kill" without --all) ensures the
+			# container is terminated.
+			if [ "${rootful}" -eq 0 ]; then
+				case "${container_manager}" in
+					*podman*)
+						${container_manager} kill "${container_name}" 2> /dev/null || :
+						;;
+				esac
+			fi
+			${container_manager} stop "${container_name}" 2> /dev/null || :
 		done
 		;;
 	n | N | No | no | NO)