Skip to content

Conversation

@keldian
Copy link
Collaborator

@keldian keldian commented Dec 29, 2025

Description

https://hub.docker.com/r/k44sh/rutorrent

Role should provide a good foundation for all crazy-max based images in case this one goes unmaintained.

How Has This Been Tested?

  • I took my "old" mondedie/rutorrent mod role and built from there. Finished it back when we announced deprecating the Saltbox role, migrated my data to this and left this running in prod as my daily driver.
  • Various debug tasks and multiple instance deployments

I'm expecting this will clash in CI with the existing role, but yoloing it.

rutorrent_role_docker_volumes_download: false
rutorrent_role_docker_volumes_default:
- "{{ rutorrent_role_paths_location }}:/config"
- "{{ lookup('role_var', '_topdir_path', default=rutorrent_role_paths_downloads_location) }}:/data:ro"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

read only?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing uses /data since TOPDIR_PATH and DOWNLOAD_PATH are both set to /mnt paths, but without this mount the image creates an anonymous volume for it (same with /passwd). ro prevents the init script creating unused directories in there, which I noticed happens on occasion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants