6 Commits

Include renames

Author	SHA1	Message	Date
Emil SimeonovandDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	5712804310	fix(prune): only remove containers older than 1 hour ... The prune service and healthcheck were force-removing ALL containers (except GITEA-ACTIONS-TASK), including molecule test containers that CI jobs were actively using. This caused "No such container" errors during molecule prepare/converge phases. Filter by RunningFor field — only remove containers showing "hour/day/week/month/year ago", excluding "minutes/seconds ago". This prevents killing molecule containers from running CI jobs while still cleaning up stale containers from crashed jobs. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	2026-08-09 01:07:38 +02:00
Emil SimeonovandDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	e1b9e09be3	fix(prune): add --filter until=1h to network prune ... docker network prune -f removes ALL unused networks, including ones that molecule tests are actively creating (e.g. 'traefik' network created during molecule create phase before containers are attached). This caused "network traefik not found" errors in CI molecule tests. Add --filter "until=1h" to only prune networks older than 1 hour, matching the container prune filter. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	2026-08-09 01:07:38 +02:00
Emil SimeonovandDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	4610e5e5c8	fix: exclude CI job containers from prune to prevent self-destruction ... The prune service and healthcheck force-remove ALL containers via "docker ps -aq | xargs -r docker rm -f", but this includes the CI job container itself (named GITEA-ACTIONS-TASK-*). Removing it causes "RWLayer of container is unexpectedly nil" errors and kills the active CI job. Exclude containers whose name starts with GITEA-ACTIONS-TASK from the force-remove step. Use "docker ps -a --format" with name filtering instead of "docker ps -aq". Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	2026-08-09 01:07:38 +02:00
Emil SimeonovandDevin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	a9e22819df	fix: force-remove running containers in prune service and healthcheck ... The docker-prune systemd service and healthcheck script used "docker container prune -f" which only removes stopped containers. Running containers from failed/interrupted molecule tests accumulated indefinitely on runner hosts, consuming disk and memory, causing CI test speed variance (12s → 39s for identical test suites). Changes: - docker-prune.service.j2: stop+rm ALL containers before system prune - runner-healthcheck.sh.j2: force-remove all containers when disk threshold is hit, use "system prune -af --volumes" for thorough cleanup - template-content/verify.yml: update assertions to match new templates The molecule_ci_guard.py in devx was also updated to run "molecule destroy" on test failure/interruption, preventing containers from being left running in the first place. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>	2026-08-09 01:07:38 +02:00
emo	185e41c49e	GRM-156: fix: harden rootless Docker daemon resilience on CI runners	2026-08-05 13:50:34 +00:00
emil	f6a4f1fe43	GRM-148: chore: bump devx to v0.41.1, update deps and runner version	2026-07-13 03:24:35 +00:00