@plankton@programming.dev to Selfhosted@lemmy.worldEnglish • edit-21 month agoI haven't had time to look into it, ok?programming.devimagemessage-square21fedilinkarrow-up1322arrow-down113
arrow-up1309arrow-down1imageI haven't had time to look into it, ok?programming.dev@plankton@programming.dev to Selfhosted@lemmy.worldEnglish • edit-21 month agomessage-square21fedilink
minus-squareidunnololzlinkfedilinkEnglish3•1 month agoTo “fix” the memory leak, just restart your server every day with a cron job /s
minus-squarejonathanlinkfedilinkEnglish2•1 month agoMy actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
minus-square@zorro@lemmy.worldlinkfedilinkEnglish2•1 month agoCron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
To “fix” the memory leak, just restart your server every day with a cron job /s
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.