Jump to content

dbsps

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by dbsps

  1. 13 hours ago, Cat_Seeder said:

     

    I understand. This may not be a very popular opinion given that lots of people are running your image in very limited devices such as an entry level NAS. However, maybe it would be worth it to break down services in separate containers, potentially binding everything together with a "do it all" docker compose file? E.g., one image with openVPN + port forwarding stuff, one image with rtorrent-ps exposing just port 5000, one image with rutorrent, one image with flood, one with privoxy, etc.

    That way you will be able to add features to individual images without worrying too much about overly bloated containers. 

    Looks very promising. The GUI is awesome. Straight out of the box beats my solution. I just need to check if it is working well with IPv6 :)

     

    Thanks for the great hint. Not sure why I haven't found the container above while looking for it :).

    I'd be fore this. I have no need of the openVPN / Privoxy or ruTorrent stuff myself but I understand if this might be a bit more work than you want to take one as well.

    • Like 1
  2. 52 minutes ago, WexfordStyle said:

    Do the recent changes affect Flood? I can't login anymore.

     

    I get the result below when I try to login and I don't see anything weird in the logs.

     

    EDIT: I lied. I found:

     

    2019-03-04 20:09:31,260 DEBG fd 22 closed, stopped monitoring <POutputDispatcher at 22886222140264 for <Subprocess at 22886221024504 with name flood-script in state RUNNING> (stdout)>
    2019-03-04 20:09:31,260 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 22886221150328 for <Subprocess at 22886221024504 with name flood-script in state RUNNING> (stderr)>
    2019-03-04 20:09:31,260 INFO exited: flood-script (exit status 0; expected)
    2019-03-04 20:09:31,260 DEBG received SIGCLD indicating a child quit
     

     

    image.png.0877cf2c85b4f093983dfdb28b7c6b59.png

    I use flood and I haven't really had any problems with the new image. Do you have static IPs set in your rtorrent.rc rather than 127.0.0.1 or similar? If so check to make sure when you updated unraid didnt assign you to a different ip. If it did you may need to update that both in rtorrent.rc as well as the flood db settings.

×
×
  • Create New...