selfhostyourtech/cubbi
2
0
Fork 0
mirror of https://github.com/Monadical-SAS/cubbi.git synced 2025-12-20 12:19:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: ensure Docker containers are always removed when closing sessions (#35)

Browse Source 
When closing sessions with already-stopped containers, the stop/kill
operation would raise an exception, preventing container.remove() from
being called. This left stopped containers in Docker even though they
were removed from cubbi's session tracking.

The fix wraps stop/kill operations in their own try-except block,
allowing the code to always reach container.remove() regardless of
whether the container was already stopped.
This commit is contained in:
Mathieu Virbel
2025-10-06 16:40:50 -06:00
committed by GitHub
parent 3795de1484
commit b788f3f52e
1 changed files with 32 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
cubbi/container.py
View File

@@ -888,35 +888,39 @@ class ContainerManager:
return False
try:
# First, close the main session container
container = self.client.containers.get(session.container_id)
try:
if kill:
container.kill()
else:
container.stop()
except DockerException:
pass
container.remove()
# Check for and close any associated network-filter container
network_filter_name = f"cubbi-network-filter-{session.id}"
try:
network_filter_container = self.client.containers.get(
network_filter_name
)
logger.info(f"Stopping network-filter container {network_filter_name}")
try:
if kill:
network_filter_container.kill()
else:
network_filter_container.stop()
except DockerException:
pass
network_filter_container.remove()
except DockerException:
# Network-filter container might not exist, which is fine
pass
self.session_manager.remove_session(session.id)
return True
except DockerException as e:
error_message = str(e).lower()
# If container is not running or already removed, still remove it from session list
if (
"is not running" in error_message
or "no such container" in error_message
@@ -951,39 +955,41 @@ class ContainerManager:
# No need for session status as we receive it via callback
# Define a wrapper to track progress
def close_with_progress(session):
if not session.container_id:
return False
try:
container = self.client.containers.get(session.container_id)
# Stop and remove container
try:
if kill:
container.kill()
else:
container.stop()
except DockerException:
pass
container.remove()
# Check for and close any associated network-filter container
network_filter_name = f"cubbi-network-filter-{session.id}"
try:
network_filter_container = self.client.containers.get(
network_filter_name
)
try:
if kill:
network_filter_container.kill()
else:
network_filter_container.stop()
except DockerException:
pass
network_filter_container.remove()
except DockerException:
# Network-filter container might not exist, which is fine
pass
# Remove from session storage
self.session_manager.remove_session(session.id)
# Notify about completion
if progress_callback:
progress_callback(
session.id,
@@ -994,7 +1000,6 @@ class ContainerManager:
return True
except DockerException as e:
error_message = str(e).lower()
# If container is not running or already removed, still remove it from session list
if (
"is not running" in error_message
or "no such container" in error_message