View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008773 | Taler | deployment and operations | public | 2024-04-25 16:58 | 2024-05-02 18:25 |
| Reporter | dvn | Assigned To | dvn | ||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Summary | 0008773: stale fuse-overlayfs processes leftover from podman | ||||
| Description | On gv.taler.net there are many idle fuse-overlayfs processes apparently leftover from podman. Running `ps aux | grep fuse-overlayfs | wc -l` resulted in 458 items. Podman should be removing these mounts when a container shuts down, but there is a known bug that prevents this under some (unknown) circumstances. See: https://github.com/containers/podman/issues/7061 We may need to implement our own cleanup of these on a cron. | ||||
| Tags | No tags attached. | ||||
|
|
I've figured out a command to clean these up: `podman unshare umount $(podman unshare mount | grep fuse | grep -v connections | cut -d' ' -f3)` |
|
|
Added a cronjob on user `container-worker` that runs the aforementioned command to remove stale fuse mounts at 05:00 every day. It has been running for a few days and appears to be working as intended. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-25 16:58 | dvn | New Issue | |
| 2024-04-25 16:58 | dvn | Status | new => assigned |
| 2024-04-25 16:58 | dvn | Assigned To | => dvn |
| 2024-04-25 17:01 | dvn | Note Added: 0022307 | |
| 2024-05-02 18:25 | dvn | Status | assigned => resolved |
| 2024-05-02 18:25 | dvn | Resolution | open => fixed |
| 2024-05-02 18:25 | dvn | Note Added: 0022329 |
