ziggy2018

Hello, binhex, I used minidlna on vm before but am quite new to docker. here is my command to start minidlna docker: docker run -d \ --net="host" \ --name=minidlna \ -v /ndisk1/media:/media \ -v /ndisk1/apps/minidlna:/config \ -v /etc/localtime:/etc/localtime:ro \ -e SCHEDULE_SCAN_DAYS=06 \ -e SCHEDULE_SCAN_HOURS=02 \ -e SCAN_ON_BOOT=no \ -e UMASK=000 \ -e PUID=0 \ -e PGID=0 \ binhex/arch-minidlna Everything seems fine, but I can't connect to webui or see the server from DLNA client. The docker host is a CentOS 7. I have a linux/transmission container running on same host w/o any issue. I changed the network to default bridge mode with port as docker run -d \ -p 8200:8200 -p 1900:1900 \ -p 1900:1900/udp \ Then I can access the webui but still can't see the server from DLNA client. Any idea? Thanks in advance, ziggy2018 === Here is minidlna.log: [2018/02/16 18:46:51] minidlna.c:1048: warn: Starting MiniDLNA version 1.2.1. [2018/02/16 18:46:51] minidlna.c:1089: warn: HTTP listening on port 8200 [2018/02/16 18:46:51] monitor.c:218: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [38] and I do not have permission to increase this limit. Please do so manually by writing a higher value into /proc/sys/fs/inotify/max_user_watches. supervisord.log: 2018-02-16 18:46:49.972923 [info] System information Linux dp_centosm 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 GNU/Linux 2018-02-16 18:46:50.017875 [info] PUID defined as '0' 2018-02-16 18:46:50.075133 [info] PGID defined as '0' 2018-02-16 18:46:50.140959 [info] UMASK defined as '000' 2018-02-16 18:46:50.187453 [info] Permissions already set for volume mappings 2018-02-16 18:46:50.242281 [info] SCAN_ON_BOOT defined as 'no' 2018-02-16 18:46:50.290276 [info] SCHEDULE_SCAN_DAYS defined as '06' 2018-02-16 18:46:50.344725 [info] SCHEDULE_SCAN_HOURS defined as '02' 2018-02-16 18:46:50.391594 [info] Starting Supervisor... 2018-02-16 18:46:50,700 CRIT Set uid to user 0 2018-02-16 18:46:50,700 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2018-02-16 18:46:50,702 INFO supervisord started with pid 7 2018-02-16 18:46:51,705 INFO spawned: 'start' with pid 56 2018-02-16 18:46:51,707 INFO spawned: 'crond' with pid 57 2018-02-16 18:46:51,707 INFO reaped unknown pid 8 2018-02-16 18:46:51,717 DEBG 'start' stdout output: [info] PID file from previous run found, deleting file /home/nobody/.config/minidlna/minidlna.pid... 2018-02-16 18:46:51,717 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-02-16 18:46:51,737 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140497282205384 for <Subprocess at 140497282206392 with name start in state RUNNING> (stdout)> 2018-02-16 18:46:51,737 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140497282203944 for <Subprocess at 140497282206392 with name start in state RUNNING> (stderr)> 2018-02-16 18:46:51,737 INFO exited: start (exit status 0; expected) 2018-02-16 18:46:51,737 DEBG received SIGCLD indicating a child quit 2018-02-16 18:46:52,739 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)