ulimit -- limitation on number of files open about docker-transmission HOT 15 CLOSED

Running into this issue on the latest tag: transmission-daemon 3.00 (bb6b5a062e)

please open a new issue and fill it out completely. you can reference this issue in your ticket but replying to something closed in 2020 is just silly.

from docker-transmission.

This limit seems to only apply to the proc running the actual daemon.

PID   USER     TIME  COMMAND
    1 root      0:00 s6-svscan -t0 /var/run/s6/services
   34 root      0:00 s6-supervise s6-fdholderd
  251 root      0:00 s6-supervise cron
  252 root      0:00 s6-supervise transmission
  257 root      0:00 /usr/sbin/crond -f -S -l 0 -c /etc/crontabs
 3137 root      0:00 /bin/bash
 4304 root      0:00 bash ./run
 4306 abc       9:53 /usr/bin/transmission-daemon -g /config -c /watch -f
 5074 root      0:00 ps

root@linuxserver-transmission1:/etc/init.d# cat /proc/4306/limits 
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        unlimited            unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             31015                31015                processes 
Max open files            1024                 1048576              files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       31015                31015                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us       

from docker-transmission.

Given this is something the user may want to control--I think the solution to this is to have an environment variable that can be set that the container is aware of. I'm not entirely sure if this limit is being set by docker itself or something in the container.

from docker-transmission.

I'm unable to reproduce this on ubuntu or debian. I'll leave this open for anyone else willing to test with syno.

from docker-transmission.

Anything you want me to grab from the affected machine?

from docker-transmission.

We have a teammember who plans to test with syno and I imagine you'll have to wait on them since this appears to only affect syno (and potentially other nas units like syno)

from docker-transmission.

@stevenboyd78 we do not allow showing piracy like this, your post has been hidden. You may re-post once you remove your blatant illegal activities from the log.

from docker-transmission.

I am facing the same on raspberry pi 2, running Raspbian lite headless.

from docker-transmission.

Check transmission/transmission#893
It will be merged soon.

from docker-transmission.

I've having this issue on

Ubuntu 18.04
Docker version 19.03.11, build 42e35e61f3
Linux nephele 5.6.3-050603-generic #202004080837 SMP Wed Apr 8 08:39:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Docker Inspect

from docker-transmission.

Same issue here. Has the merge been approved?

from docker-transmission.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-transmission.

I try to build own version (transmission 3.00+) to solve this problem.
https://github.com/gaozhitw/docker-transmission

from docker-transmission.

This image has been on 3+ for a while now

from docker-transmission.

Running into this issue on the latest tag: transmission-daemon 3.00 (bb6b5a062e)

from docker-transmission.