Contributors to this thread:

Trying to mass-delete older posts and shares on my #ktistec instance without prior backup turned out to be a bad idea

The docker container running on my tiny 1 vCPU, 1GB RAM VPS suddently started crashing and restarting every few seconds.

Turns out, ktistec is doing some(?) tasks in the background now, hogging the CPU and loads of RAM, which eventually leads to crashing the container. Creating a swapfile stabilized the situation until the cleanup(?) tasks are done. We will see whenever it finishes.

Remember: never start fiddling without doing prior backups...

Well, it got back to the normal resource usage (<1% and only a few MB RAM) in the past 3 hours or so... All good, I did not screw up my instance then :D