mkono87 Posted March 25, 2018 Share Posted March 25, 2018 (edited) Just installed this and tested downloading a file. File completed but I cannot move it as it says I have no permissions. Says I need permission for Nas/nobody Also noticed I cant open settings.json as its protected as well. Cant delete any of files in my completed folder. The torrent share I created is public. This was while trying to cut from my torrents share and paste into iso share. I can however, copy it to my desktop then paste it into the iso share. Edited March 25, 2018 by mkono87 Quote Link to comment
trurl Posted March 25, 2018 Share Posted March 25, 2018 40 minutes ago, mkono87 said: I cant open settings.json as its protected as well You will have to stop the docker to edit settings.json. You might have to use Config File Editor plugin since it will have root access and it will also make sure the saved file has linux line endings unlike some Windows editor like Notepad. To fix permissions on existing files use Docker Safe New Perms in Tools. Quote Link to comment
M4st3r Posted March 26, 2018 Share Posted March 26, 2018 I would like to report that the transmission container seems to be broken: when I try to connect to the web-gui, I receive the error "too many redirects" and I can't see anything else. I've tried to uninstall and reinstall the container, but w/out seeing any difference. Quote Link to comment
sparklyballs Posted March 26, 2018 Share Posted March 26, 2018 3 minutes ago, M4st3r said: I would like to report that the transmission container seems to be broken: when I try to connect to the web-gui, I receive the error "too many redirects" and I can't see anything else. I've tried to uninstall and reinstall the container, but w/out seeing any difference. that is more likely a local issue with your browser clear browser cache etc Quote Link to comment
M4st3r Posted March 26, 2018 Share Posted March 26, 2018 21 minutes ago, sparklyballs said: that is more likely a local issue with your browser clear browser cache etc Many thanks, I thought already done it, but Quote Link to comment
FrostyWolf Posted March 26, 2018 Share Posted March 26, 2018 I am getting a bunch of: I believe this info might be helpful reading other people that have this same issue: Not sure how to proceed. Quote Link to comment
sparklyballs Posted March 26, 2018 Share Posted March 26, 2018 18 minutes ago, FrostyWolf said: I am getting a bunch of: I believe this info might be helpful reading other people that have this same issue: Not sure how to proceed. that's something you need to sort on the host and is not anything to do with our image specifically Quote Link to comment
FrostyWolf Posted March 26, 2018 Share Posted March 26, 2018 1 hour ago, sparklyballs said: that's something you need to sort on the host and is not anything to do with our image specifically Ok thank you, I'll ask in main unraid support then. Quote Link to comment
7thSon Posted April 16, 2018 Share Posted April 16, 2018 (edited) I'm having issues starting today with the transmission container running on my Synology NAS, something had happened in the past few days and I couldn't connect using transmission-remote-gui to port 9091 anymore. When I check the container activity with "docker logs -ft transmission" I see that it keeps looping over and over with some cron jobs: 2018-04-16T22:26:00.118912370Z crond[230]: wakeup dt=60 2018-04-16T22:26:00.119820664Z crond[230]: file root: 2018-04-16T22:26:00.120240118Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:26:00.120578958Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:26:00.120908051Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:26:00.121254684Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:26:00.121692976Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:26:00.122274140Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:27:00.119934553Z crond[230]: wakeup dt=60 2018-04-16T22:27:00.120979449Z crond[230]: file root: 2018-04-16T22:27:00.121349029Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:27:00.121689309Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:27:00.122074448Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:27:00.122412187Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:27:00.122886813Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:27:00.123194023Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:28:00.120922269Z crond[230]: wakeup dt=60 2018-04-16T22:28:00.121834883Z crond[230]: file root: 2018-04-16T22:28:00.122234549Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:28:00.122546785Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:28:00.122811917Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:28:00.123184936Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:28:00.123513314Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:28:00.123795709Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:29:00.123897329Z crond[230]: wakeup dt=60 2018-04-16T22:29:00.124822063Z crond[230]: file root: 2018-04-16T22:29:00.125267840Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:29:00.125683464Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:29:00.126120896Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:29:00.126486089Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:29:00.126885788Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:29:00.127262263Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:30:00.125966011Z crond[230]: wakeup dt=60 2018-04-16T22:30:00.127182959Z crond[230]: file root: 2018-04-16T22:30:00.127579155Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:30:00.127943840Z crond[230]: job: 0 run-parts /etc/periodic/15min 2018-04-16T22:30:00.128167902Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:30:00.128470224Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:30:00.128774032Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:30:00.129120691Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:30:00.129423172Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:30:00.129726678Z crond[1148]: child running /bin/sh 2018-04-16T22:30:00.129956405Z crond[230]: USER root pid 1148 cmd run-parts /etc/periodic/15min 2018-04-16T22:30:10.128887516Z crond[230]: wakeup dt=10 2018-04-16T22:31:00.129923726Z crond[230]: wakeup dt=50 2018-04-16T22:31:00.131015858Z crond[230]: file root: 2018-04-16T22:31:00.131366878Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:31:00.131534077Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:31:00.131913003Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:31:00.132235543Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:31:00.132560756Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:31:00.132960474Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:32:00.132896426Z crond[230]: wakeup dt=60 2018-04-16T22:32:00.134140080Z crond[230]: file root: 2018-04-16T22:32:00.134492799Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:32:00.134721947Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:32:00.135106433Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:32:00.135405947Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:32:00.135675820Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:32:00.136016803Z crond[230]: line /config/blocklist-update.sh 2>&1 2018-04-16T22:33:00.134923640Z crond[230]: wakeup dt=60 2018-04-16T22:33:00.135957225Z crond[230]: file root: 2018-04-16T22:33:00.136361075Z crond[230]: line run-parts /etc/periodic/15min 2018-04-16T22:33:00.136682863Z crond[230]: line run-parts /etc/periodic/hourly 2018-04-16T22:33:00.137031869Z crond[230]: line run-parts /etc/periodic/daily 2018-04-16T22:33:00.137355044Z crond[230]: line run-parts /etc/periodic/weekly 2018-04-16T22:33:00.137653641Z crond[230]: line run-parts /etc/periodic/monthly 2018-04-16T22:33:00.137988072Z crond[230]: line /config/blocklist-update.sh 2>&1 Other than that all I get from the very start of the container launch is the below. The watch dir not having any space is peculiar, I have no idea why that is, the folder has permissions and theres definitely space left. 2018-04-16T22:12:56.038035807Z ------------------------------------- 2018-04-16T22:12:56.038205625Z GID/UID 2018-04-16T22:12:56.038315851Z ------------------------------------- 2018-04-16T22:12:56.039945533Z 2018-04-16T22:12:56.040247858Z User uid: 1024 2018-04-16T22:12:56.040461942Z User gid: 100 2018-04-16T22:12:56.040669955Z ------------------------------------- 2018-04-16T22:12:56.040922241Z 2018-04-16T22:12:56.046951854Z [cont-init.d] 10-adduser: exited 0. 2018-04-16T22:12:56.047264525Z [cont-init.d] 20-config: executing... 2018-04-16T22:12:56.060947838Z [cont-init.d] 20-config: exited 0. 2018-04-16T22:12:56.061185440Z [cont-init.d] done. 2018-04-16T22:12:56.064945582Z [services.d] starting services 2018-04-16T22:12:56.082927904Z [services.d] done. 2018-04-16T22:12:56.085941752Z crond[230]: crond (busybox 1.27.2) started, log level 0 2018-04-16T22:12:56.086303692Z crond[230]: user:root entry:*/15 * * * * run-parts /etc/periodic/15min 2018-04-16T22:12:56.087930269Z crond[230]: user:root entry:0 * * * * run-parts /etc/periodic/hourly 2018-04-16T22:12:56.088277033Z crond[230]: user:root entry:0 2 * * * run-parts /etc/periodic/daily 2018-04-16T22:12:56.088539751Z crond[230]: user:root entry:0 3 * * 6 run-parts /etc/periodic/weekly 2018-04-16T22:12:56.088765925Z crond[230]: user:root entry:0 5 1 * * run-parts /etc/periodic/monthly 2018-04-16T22:12:56.089080773Z crond[230]: user:root entry:0 3 * * * /config/blocklist-update.sh 2>&1 2018-04-16T22:12:59.978902938Z [2018-04-17 00:12:59.976] Transmission 2.93 (3c5870d4f5) started (session.c:740) 2018-04-16T22:12:59.979630357Z [2018-04-17 00:12:59.977] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:971) 2018-04-16T22:12:59.979832088Z [2018-04-17 00:12:59.977] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1213) 2018-04-16T22:12:59.980159973Z [2018-04-17 00:12:59.977] RPC Server Password required (rpc-server.c:1220) 2018-04-16T22:12:59.980367358Z [2018-04-17 00:12:59.977] UDP Failed to set receive buffer: requested 4194304, got 425984 (tr-udp.c:84) 2018-04-16T22:12:59.980512177Z [2018-04-17 00:12:59.977] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:89) 2018-04-16T22:12:59.980663913Z [2018-04-17 00:12:59.977] UDP Failed to set send buffer: requested 1048576, got 425984 (tr-udp.c:95) 2018-04-16T22:12:59.980796676Z [2018-04-17 00:12:59.977] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:100) 2018-04-16T22:12:59.981037827Z [2018-04-17 00:12:59.977] DHT Reusing old id (tr-dht.c:307) 2018-04-16T22:12:59.981287222Z [2018-04-17 00:12:59.977] DHT Bootstrapping from 148 IPv4 nodes (tr-dht.c:156) 2018-04-16T22:12:59.981463145Z [2018-04-17 00:12:59.977] Using settings from "/config" (daemon.c:528) 2018-04-16T22:12:59.981591487Z [2018-04-17 00:12:59.977] Saved "/config/settings.json" (variant.c:1266) 2018-04-16T22:12:59.981725141Z [2018-04-17 00:12:59.977] Saved pidfile "/transmission.pid" (daemon.c:543) 2018-04-16T22:12:59.981886441Z [2018-04-17 00:12:59.977] transmission-daemon requiring authentication (daemon.c:554) 2018-04-16T22:12:59.982121182Z [2018-04-17 00:12:59.977] Watching "/watch" for new .torrent files (daemon.c:573) 2018-04-16T22:12:59.982522411Z [2018-04-17 00:12:59.977] watchdir:inotify Failed to setup watchdir "/watch": No space left on device (28) (watchdir-inotify.c:176) 2018-04-16T22:12:59.982740871Z [2018-04-17 00:12:59.977] Loaded __ torrents (session.c:2034) 2018-04-16T22:12:59.982918527Z [2018-04-17 00:12:59.977] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70) 2018-04-16T22:12:59.983168351Z [2018-04-17 00:12:59.977] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70) My docker settings in JSON format from the NAS: { "cap_add" : [], "cap_drop" : [], "cmd" : "", "cpu_priority" : 50, "devices" : null, "enable_publish_all_ports" : false, "enable_restart_policy" : false, "enabled" : false, "entrypoint_default" : "/init", "env_variables" : [ { "key" : "TRANSMISSION_WATCH_DIR_ENABLED", "value" : "false" }, { "key" : "PATH", "value" : "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" }, { "key" : "PS1", "value" : "$(whoami)@$(hostname):$(pwd)$ " }, { "key" : "HOME", "value" : "/root" }, { "key" : "TERM", "value" : "xterm" }, { "key" : "TZ", "value" : "Europe/Berlin" }, { "key" : "PGID", "value" : "100" }, { "key" : "PUID", "value" : "1024" } ], "exporting" : false, "id" : "77b1d0b0c044071360b962d48ac8471f1c15c4c93ca0e97eb7cdeea43dd2ff37", "image" : "linuxserver/transmission:latest", "is_ddsm" : false, "is_package" : false, "links" : [], "memory_limit" : 0, "name" : "transmission", "network" : [ { "driver" : "bridge", "name" : "bridge" } ], "network_mode" : "bridge", "port_bindings" : [ { "container_port" : 8888, "host_port" : 0, "type" : "tcp" }, { "container_port" : 9091, "host_port" : 0, "type" : "tcp" } ], "privileged" : false, "shortcut" : { "enable_shortcut" : true, "enable_status_page" : false, "enable_web_page" : true, "web_page_url" : "http://192.168.1.100:9091" }, "ulimits" : null, "use_host_network" : false, "volume_bindings" : [ { "host_volume_file" : "/docker/watch", "mount_point" : "/watch", "type" : "rw" }, { "host_volume_file" : "/docker/incomplete", "mount_point" : "/incomplete", "type" : "rw" }, { "host_volume_file" : "/docker/downloads", "mount_point" : "/downloads", "type" : "rw" }, { "host_volume_file" : "/homes/admin/.config/transmission", "mount_point" : "/config", "type" : "rw" }, { "host_volume_file" : "/scripts/filebot", "mount_point" : "/volume1/scripts/filebot", "type" : "rw" } ], "volumes_from" : null } Any ideas what to try next? I can't seem to figure out why the cron job just loops and loops, Edited April 16, 2018 by 7thSon Quote Link to comment
trurl Posted April 16, 2018 Share Posted April 16, 2018 9 minutes ago, 7thSon said: I'm having issues starting today with the transmission container running on my Synology NAS From the very first post in this support thread: Quote If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support. Quote Link to comment
7thSon Posted April 17, 2018 Share Posted April 17, 2018 7 hours ago, trurl said: From the very first post in this support thread: My bad, it was very late when posting last night. Will go to linuxserver.io forum instead. Quote Link to comment
FieldGenEJ Posted April 18, 2018 Share Posted April 18, 2018 Hey guys I'm getting ERR_TOO_MANY_REDIRECTS when I try to access the Transmission WebGUI. Anyone run into this before? I've tried restarting the docker as well as deleting/reinstalling it to no avail. Any ideas would be appreciated. Thanks! Quote Link to comment
cdevlin Posted May 5, 2018 Share Posted May 5, 2018 I've just updated to version to 2.94 of Transmission but need to go back to version 2.93. Is there any way of doing this? Thanks for any help. Quote Link to comment
natecook Posted May 6, 2018 Share Posted May 6, 2018 (edited) On 5/5/2018 at 5:17 AM, cdevlin said: I've just updated to version to 2.94 of Transmission but need to go back to version 2.93. Is there any way of doing this? Thanks for any help. Set your repository to linuxserver/transmission:121 (https://hub.docker.com/r/linuxserver/transmission/tags/) Without specifying the version tag, it will pull the latest version. 121 is the most recent Linuxserver version with 2.93. Edited May 6, 2018 by natecook Quote Link to comment
cdevlin Posted May 6, 2018 Share Posted May 6, 2018 2 hours ago, natecook said: Set your repository to linuxserver/transmission:121 (https://hub.docker.com/r/linuxserver/transmission/tags/) Without specifying the version tag, it will pull the latest version. 121 is the most recent Linuxserver version with 2.93. Ahh, thanks for that natecook. Worked a treat. Quote Link to comment
htpcguru Posted June 8, 2018 Share Posted June 8, 2018 root@UnRaid:~# docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/transmission Linuxserver.io version:- 126 Build-date:- June-01-2018-22:08:29-UTC Container version 126 contains Transmission 2.94. I need to downgrade Transmission to 2.93 as one of my trackers rejects the latest Transmission 2.94. How would I do that? Quote Link to comment
CHBMB Posted June 8, 2018 Share Posted June 8, 2018 root@UnRaid:~# docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/transmissionLinuxserver.io version:- 126 Build-date:- June-01-2018-22:08:29-UTC Container version 126 contains Transmission 2.94. I need to downgrade Transmission to 2.93 as one of my trackers rejects the latest Transmission 2.94. How would I do that? By reading the two posts above yours. Quote Link to comment
htpcguru Posted June 8, 2018 Share Posted June 8, 2018 16 hours ago, CHBMB said: 17 hours ago, htpcguru said: root@UnRaid:~# docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/transmissionLinuxserver.io version:- 126 Build-date:- June-01-2018-22:08:29-UTC Container version 126 contains Transmission 2.94. I need to downgrade Transmission to 2.93 as one of my trackers rejects the latest Transmission 2.94. How would I do that? By reading the two posts above yours. Awesome, that was easy! Quote Link to comment
BelgarionNL Posted June 30, 2018 Share Posted June 30, 2018 Hi running latest the latest docker image of transmission together with the latest version of unraid and I see a linear increase in memory usage in grafana. see attached image. how can I fix this? all help is appreciated thx. Quote Link to comment
kesm Posted October 29, 2018 Share Posted October 29, 2018 Hi, I'm pretty new to unraid (Unraid OS Trial 29 days remaining ) and I can't find where I can change the webui for transmission. I'm trying to switch from classic ui to Transmission Web Control or Combustion but I can't get it working. I tried install scription from TWC in putty with transmission running or not, from console with transmission running and by replacing web folder in /mnt/disk1/appdata/transmission /mnt/user/appdata/transmission but nothing works. I search online but found nothing, did someone succeed to change original web ui? Quote Link to comment
trurl Posted October 29, 2018 Share Posted October 29, 2018 8 minutes ago, kesm said: Hi, I'm pretty new to unraid (Unraid OS Trial 29 days remaining ) and I can't find where I can change the webui for transmission. I'm trying to switch from classic ui to Transmission Web Control or Combustion but I can't get it working. I tried install scription from TWC in putty with transmission running or not, from console with transmission running and by replacing web folder in /mnt/disk1/appdata/transmission /mnt/user/appdata/transmission but nothing works. I search online but found nothing, did someone succeed to change original web ui? In order for any command to work inside a container, you must be at a command line inside the container. Installing TWC in Unraid won't help with getting it installed to the linux running inside the transmission container. See here: You might have better luck with Combustion, since it has more ways to do the installation. Note that even if you get either of these to work it won't survive an update or reinstall of the container. I just use the Transmission Remote GUI application. Quote Link to comment
DZMM Posted November 6, 2018 Share Posted November 6, 2018 On 7/7/2017 at 12:31 AM, smdion said: I found this script and put in my config folder, then added the following items to my settings.json "script-torrent-done-enabled": true, "script-torrent-done-filename": "/config/unrar.sh", @smdion the link is broken - can you share the script again please. Quote Link to comment
7thSon Posted November 14, 2018 Share Posted November 14, 2018 (edited) I'm trying to use the transmission script-torrent-done functionality to start another docker container from inside the transmission container. To do this I've mounted the /var/run/docker.sock, but there are permissions issues after that. My script is located in "/config/postproc.sh", and is run by the user "abc" presumably. I've tried setting the postproc script to print "whoami", but it shows up blank mostly, however I think once it did manage to print "abc" for some reason. These are the recurring errors I'm getting, the first one is obvious since /root/.docker/config.json doesn't even exist, the question is, what user is trying to access it, and why doesn't it exist? WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied The second one is permission error for docker.sock, perhaps because "abc" isn't actually the user trying to access it? docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.38/containers/create?name=filebot: dial unix /var/run/docker.sock: connect: permission denied. So looking in /etc/passwd I can see that the abc users' home folder is /config. I installed bash and set the abc users shell to /bin/bash in my Dockerfile (below), and created this .bashrc in /config for abc to source: if [ -e /var/run/docker.sock ]; then sudo chown abc:docker /var/run/docker.sock; fi if [ -e /root/.docker/config.json ]; then sudo chown abc:docker /root/.docker/config.json; fi Dockerfile: FROM linuxserver/transmission:latest RUN apk update RUN apk add docker bash RUN usermod -a -G docker abc RUN chsh --shell /bin/bash abc What more do I need to get the docker socket to be available for the user running a script-torrent-done script? Edited November 14, 2018 by 7thSon Quote Link to comment
kesm Posted November 16, 2018 Share Posted November 16, 2018 On 10/29/2018 at 5:43 PM, kesm said: Hi, I'm pretty new to unraid (Unraid OS Trial 29 days remaining ) and I can't find where I can change the webui for transmission. I'm trying to switch from classic ui to Transmission Web Control or Combustion but I can't get it working. I tried install scription from TWC in putty with transmission running or not, from console with transmission running and by replacing web folder in /mnt/disk1/appdata/transmission /mnt/user/appdata/transmission but nothing works. I search online but found nothing, did someone succeed to change original web ui? I've been able to install a new web ui by doing this : Update container Add another Path, Port, Variable, Label or Device Add variable named "TRANSMISSION_WEB_HOME" with value "/web" without "" Add path named "/web" with value "thepathwhereyousavedyourwebui" Save Transmission have a new web ui after a refresh cache from browser 1 Quote Link to comment
Vaseer Posted November 25, 2018 Share Posted November 25, 2018 Transmission, Extra Parameters not applied to container. I am trying to set Extra Parameters --dns=208.67.222.222 and when I hit Save or Apply I get response: Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='transmission' --net='br0' --ip='10.0.0.32' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e 'TCP_PORT_9091'='9091' -e 'TCP_PORT_51413'='51413' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/disks/downloads/':'/downloads':'rw,slave' -v '/mnt/disks/downloads/transmission-watch/':'/watch':'rw,slave' -v '/mnt/cache/docker/appdata/Transmission/':'/config':'rw' --dns=208.67.222.222 'linuxserver/transmission' The command finished successfully! But when I check container config via WebUI, Extra Parameters field is empty. I have problem with Transmission container only. unRAID 6.6.5 Transmission docker container: latest (updated minutes ago) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.