plankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-27 days agoI haven't had time to look into it, ok?programming.devimagemessage-square21linkfedilinkarrow-up1325arrow-down113file-text
arrow-up1312arrow-down1imageI haven't had time to look into it, ok?programming.devplankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-27 days agomessage-square21linkfedilinkfile-text
minus-squareidunnololz@lemmy.worldlinkfedilinkEnglisharrow-up2·7 days agoTo “fix” the memory leak, just restart your server every day with a cron job /s
minus-squarezorro@lemmy.worldlinkfedilinkEnglisharrow-up2·6 days agoCron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up1·6 days agoMy actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
To “fix” the memory leak, just restart your server every day with a cron job /s
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅