Exploding Heads - Help hold the ruling class accountable
exploding-heads.com

I ran out of space on my instance which is hosted on linode. I used their automated system to upgrade the node so it had more hard drive space.

Since I did that, images have not displayed on my instance. Either from existing posts or new posts. How do I fix this?

I submited a question on GitHub https://github.com/LemmyNet/lemmy/issues/2637 and was asked to provide a “the docker compose logs” and to try restarting “docker compose”.

I rebooted the virtual server, which I assume would restart the docker compose. If not, how do I restart it?

Also can you give me the exact commands to:

  • do a docker compose restart and where I do it from
  • generate the docker compose logs and how to limit the size if it is likely to be to big to upload to github and where to run the commands from.

Thanks in advance for your help.

  • poVoq@slrpnk.net
    1·
    2 years ago

    Try the force-recreate option to make sure you are not only restarting the containers but actually recreating them.

    • letstryOP
      1·
      2 years ago

      I ran the force-recreate option.

      Now when I go to the instance I get a spinning wheel where the posts would normally appeal. I am assuming this is just rebuilding all the pages and may take some time? Would take be correct?

      • poVoq@slrpnk.net
        1·
        2 years ago

        no that looks more like it has issues connecting to the database. Maybe the database container got renamed?

        • letstryOP
          1·
          2 years ago

          so what should I do now?

          Should I restore the backup from before I ran the recreate command or do something else?