binhex / arch-minidlna

Docker build script for Arch Linux base with MiniDLNA

Application

MiniDLNA

Description

ReadyMedia (formerly known as MiniDLNA) is a simple media server software, with the aim of being fully compliant with DLNA/UPnP-AV clients. It is developed by a NETGEAR employee for the ReadyNAS product line.

Build notes

Latest stable release of MiniDLNA.

Usage

docker run -d \
    --net="host" \
    --name=<container name> \
    -v <path for media files>:/media \
    -v <path for config files>:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e SCHEDULE_SCAN_DAYS=<00-06> \
    -e SCHEDULE_SCAN_HOURS=<00-23> \
    -e SCAN_ON_BOOT=<yes|no> \
    -e UMASK=<umask for created files> \
    -e PUID=<uid for user> \
    -e PGID=<gid for user> \
    binhex/arch-minidlna

Please replace all user variables in the above command defined by <> with the correct values.

Access application

N/A, CLI only.

Example

docker run -d \
    --net="host" \
    --name=minidlna \
    -v /media/pictures:/media \
    -v /apps/docker/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

Notes

User ID (PUID) and Group ID (PGID) can be found by issuing the following command for the user you want to run the container as:-

id <username>

You cannot specify the port the docker container uses, it requires full access to the hosts nic and thus the -p flag is not used. Additional configuration for this application can be done by modifying the /config/minidlna.conf file.

---

If you appreciate my work, then please consider buying me a beer :D

Documentation | Support forum

arch-minidlna's Issues

Update dockerhub image

The actual dockerhub image was updated more than 10 months ago, could you update it with the latest version on this repo?

It would be awesome! Thanks in advance and good work

how mount host dir regarding not matching uid's problems?

do you have some best practice for handling failure of host mounts in case of different ui's...
Because container runs root (uid=0) and dlna meadia is often in user space with (uid=1000>)
So it's tricky to use your image out of the box... Any ideas?

Fresh install doesn't start uPnP server

I installed the app on my unRAID from the store and kept all the default settings.
The docker started fine but it doesn't seem to be listening for connections.

text  error  warn  system  array  login  

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-12-29 23:47:00.078112 [info] Host is running unRAID
2022-12-29 23:47:00.120639 [info] System information Linux Tower 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-12-29 23:47:00.172407 [info] OS_ARCH defined as 'x86-64'
2022-12-29 23:47:00.222824 [info] PUID defined as '99'
2022-12-29 23:47:00.320660 [info] PGID defined as '100'
2022-12-29 23:47:00.423808 [info] UMASK defined as '000'
2022-12-29 23:47:00.472180 [info] Permissions already set for '/config'
2022-12-29 23:47:00.533387 [info] Deleting files in /tmp (non recursive)...
2022-12-29 23:47:00.590325 [info] SCAN_ON_BOOT defined as 'no'
2022-12-29 23:47:00.639164 [info] SCHEDULE_SCAN_DAYS defined as '06'
2022-12-29 23:47:00.687910 [info] SCHEDULE_SCAN_HOURS defined as '02'
2022-12-29 23:47:00.745614 [info] Starting Supervisor...
2022-12-29 23:47:01,396 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing
2022-12-29 23:47:01,396 INFO Set uid to user 0 succeeded
2022-12-29 23:47:01,402 INFO supervisord started with pid 7
2022-12-29 23:47:02,407 INFO spawned: 'crond' with pid 80
2022-12-29 23:47:02,412 INFO spawned: 'start' with pid 81
2022-12-29 23:47:02,412 INFO reaped unknown pid 8 (exit status 0)
2022-12-29 23:47:02,966 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22547819191488 for <Subprocess at 22547819186208 with name start in state STARTING> (stdout)>
2022-12-29 23:47:02,967 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22547819191536 for <Subprocess at 22547819186208 with name start in state STARTING> (stderr)>
2022-12-29 23:47:02,967 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-12-29 23:47:02,968 INFO exited: start (exit status 0; expected)
2022-12-29 23:47:02,968 DEBG received SIGCHLD indicating a child quit
2022-12-29 23:47:03,970 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)