I was using LibReddit to check in once in a while, and it died today and Teddit instances are giving error 429 too, so yeah, no more Reddit from now on

  • Mugmoor@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    docker pull libreddit/libreddit

    docker run -d --name libreddit -p 80:8080 libreddit/libreddit

    Notice the port mapping. If you ran this command, youre binding port 80 to the docker container’s port 8080. You can set it to whatever you like.

    As for the .toml, I didnt even bother. That just sets the instance defaults, but you can change those on a per-user basis from within LibReddit.

    • venusenvy47@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      That’s the command I used.

      sudo docker run -d --name libreddit -p 80:8080 libreddit/libreddit

      Then I checked the port traffic with sudo lsof -i -P | grep -i “listen” and saw it running on port 80. And I could only connect to it from my browser on port 80. But it doesn’t matter, I switched to teddit in Docker and have it running with a compose file, so I’m set.

      • Mugmoor@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        Yes that command is binding port 80 to 8080. If you wanted it to run on port 8080 you’d run this command instead:

        sudo docker run -d --name libreddit -p 8080:8080 libreddit/libreddit

        The first port number is your local network, the second is the internal docker network.

        And yes, using a compose file is what I would recommend.

        • venusenvy47@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Oops. I don’t fully understand Docker and I misread the instructions for selecting the port.

          On a related topic, is there any reason why I had to use “sudo” to run these Docker commands? I tried both without sudo and they both failed.