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
    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
      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.

        • venusenvy47
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Yes, I actually used Portainer on my VPS when I was learning Docker last year. It makes some things easier, but it does add another layer of complexity, learning to navigate the Portainer interface and setting up Stacks to deploy your compose files. With my home server I was trying to experiment with “the natural Docker” procedure.