View Issue Details

IDProjectCategoryView StatusLast Update
0008876Talerdeployment and operationspublic2024-08-28 21:31
Reporterdvn Assigned Todvn Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.13Fixed in Version0.13 
Summary0008876: Podman images & volumes taking up excess storage
DescriptionThe users with the most heavy usage of podman measured on 2024-05-14:

```
205G container-worker
97G demo
37G taler-test
32G head
```
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

dvn

2024-05-28 14:08

reporter   ~0022481

I've added a cronjob on user container-worker to run `podman system prune -a -f --volumes` at 4am everyday. Will consider doing the same on the others, but want to be careful not to preemptively destroy volumes still in use.

dvn

2024-05-28 14:53

reporter   ~0022483

The same cronjob is set on user "head" now.

Issue History

Date ModifiedUsernameFieldChange
2024-05-28 14:08dvnNew Issue
2024-05-28 14:08dvnStatusnew => assigned
2024-05-28 14:08dvnAssigned To => javier.sepulveda
2024-05-28 14:08dvnNote Added: 0022481
2024-05-28 14:53dvnNote Added: 0022483
2024-05-29 08:53javier.sepulvedaStatusassigned => acknowledged
2024-05-29 08:54javier.sepulvedaAssigned Tojavier.sepulveda => dvn
2024-06-24 00:46dvnStatusacknowledged => informing
2024-06-24 00:46dvnResolutionopen => fixed
2024-08-26 20:29Christian GrothoffTarget Version => 0.13
2024-08-26 20:29Christian GrothoffFixed in Version => 0.13
2024-08-28 21:31Christian GrothoffStatusinforming => closed