-
Just that, wondering if there is a way to run the transmission-remote in the container for scripting? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
yes: transmission-remote ${HOSTNAME} -n < username >:< password > -V with export TR_AUTH="< username >:< password >" |
Beta Was this translation helpful? Give feedback.
-
I use podman rootless containers and run transmission on a separate user than my main user. This is what I do to run it from outside the container:
Note: Step 2 allows you to run transmission-remote, tra (transmission-remote -a) and trl (transmission-remote -l) from your regular user. Note: Step 3 allows your regular user to use sudo to run commands as your transmission container's user without having to enter a password. Note: If you don't use a separate user to run your transmission container, the first line in your alias file "transmission-remote should be only:
Note: just replace podman with docker if that's what you use |
Beta Was this translation helpful? Give feedback.
I use podman rootless containers and run transmission on a separate user than my main user.
This is what I do to run it from outside the container:
Make sure you name your container when you create it (--name=transmission), so you can always refer to your container using the same name (instead of, e.g. 9eafbc74573b, which will change with updates, etc)
Add the following to your aliases (~/.alias for open_SUSE, ~/bash_aliases for ubuntu)