Having an issue with pictrs after full disk
The virtual disk for my lemmy instance filled up which caused lemmy to throw a lot of errors. I resized the disk and expanded the filesystem but now the pictrs container is constantly restarting.
<span style="color:#323232;">root@Lemmy:/srv/lemmy# le
</span><span style="color:#323232;">less lessecho lessfile lesskey lesspipe let letsencrypt lexgrog
</span><span style="color:#323232;">root@Lemmy:/srv/lemmy# ls
</span><span style="color:#323232;">leemyalone.org
</span><span style="color:#323232;">root@Lemmy:/srv/lemmy# cd leemyalone.org/
</span><span style="color:#323232;">root@Lemmy:/srv/lemmy/leemyalone.org# docker-compose ps
</span><span style="color:#323232;"> Name Command State Ports
</span><span style="color:#323232;">-------------------------------------------------------------------------------------------------------------------------
</span><span style="color:#323232;">leemyaloneorg_lemmy-ui_1 docker-entrypoint.sh /bin/ ... Up 1234/tcp
</span><span style="color:#323232;">leemyaloneorg_lemmy_1 /app/lemmy Up
</span><span style="color:#323232;">leemyaloneorg_pictrs_1 /sbin/tini -- /usr/local/b ... Restarting
</span><span style="color:#323232;">leemyaloneorg_postfix_1 /root/run Up 25/tcp
</span><span style="color:#323232;">leemyaloneorg_postgres_1 docker-entrypoint.sh postgres Up 5432/tcp
</span><span style="color:#323232;">leemyaloneorg_proxy_1 /docker-entrypoint.sh ngin ... Up 80/tcp, 0.0.0.0:3378->8536/tcp,:::3378->8536/tcp
</span>