Many instances purged their images after the lemmyshitpost incident. Perhaps that’s what you’re seeing.

Ah my bad. Memmy didn’t display the code block in your OP or this post. I see it on the web version.

That error might be less about needing X11 and more about wanting D-Bus. Since D-Bus isn’t running, it’s trying to start it by itself using X11, which also doesn’t work.

Does the error actually make Lemmy quit out?

FWIW I have a sanitised copy of my Lemmy k8s config on Gitlab that might help: https://gitlab.com/conorab/k8s-lemmy

What’s the error you’re seeing?

This also helps mitigate the risk of people posting CSAM to attack other communities which your instance is subscribed to right? If you instance never cached the image, there’s no clean-up you have to do on your end provided the original instance removes the image from their server.

As you’ve mentioned, it makes sense for larger instances to have a cache, but smaller instance (especially single-user instances) may actually be better off not caching at all and just hosting their own images. As a more long-term solution which can add to this patch, it would be good if Lemmy did 2 things:

1. Separated the image cache for images from other instances so it can be cleared automatically on a schedule. E.g. Images which are a local cache are deleted after X days. Yes there are proper caching algorithms used in filesystems which would be better long-term, but a quick solution for this is probably better than no solution.
2. Periodically check for images which were uploaded by your own users to see if they are being referenced by any posts or comments. If not, delete them. I would imagine this could be a fairly intense operation so limiting this more fine-grained approach to images uploaded by your own users and taking the more liberal approach with cached images may help performance.