devteam/sharenet
3
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Add better handling to safe storage pruning step
Some checks failed
Podman Rootless Demo / test-backend (push) Has been skipped
Details
Podman Rootless Demo / test-frontend (push) Successful in 11s
Details
Podman Rootless Demo / build-backend (push) Has been skipped
Details
Podman Rootless Demo / build-frontend (push) Failing after 33s
Details
Podman Rootless Demo / deploy-prod (push) Has been skipped
Details

Browse source
This commit is contained in:
continuist 2025-09-21 13:53:07 -04:00
parent 87be8433c6
commit 852e1bde51
1 changed files with 12 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
.forgejo/workflows/ci.yml
View file

@ -210,11 +210,20 @@ jobs:
- name: Safe storage pruning
run: |
# Stop and remove any running containers first
podman --remote ps -aq | xargs -r podman --remote rm -f 2>/dev/null || true
# Then prune system
set -x # Enable debug output
# List and remove any running containers first
echo "=== Removing running containers ==="
podman --remote ps -aq | while read -r container; do
echo "Removing container: $container"
podman --remote rm -f "$container" || echo "Failed to remove container $container"
done
echo "=== Pruning system ==="
podman --remote system prune -f
echo "=== Storage status after pruning ==="
podman --remote system df
- name: Build frontend container image
run: |
# Create temp directory on larger filesystem