geekduck / docker-minidlna

MiniDLNA docker image

MiniDLNA

MiniDLNA is a simple media server software, with the aim of being fully compliant with DLNA/UPnP-AV clients.

MiniDLNA Docker Images

This image is based on Alpine Linux.

Usage

Example:

docker run -d --name minidlna \
  --net=host \
  -v <PATH_TO_MUSIC_DIR>:/opt/Music \
  -v <PATH_TO_VIDEOS_DIR>:/opt/Videos \
  -v <PATH_TO_PICUTRES_DIR>:/opt/Pictures \
  geekduck/minidlna

If you want to overwrite a config file:

docker run -d --name minidlna \
  --net=host \
  -v <PATH_TO_MUSIC_DIR>:/opt/Music \
  -v <PATH_TO_VIDEOS_DIR>:/opt/Videos \
  -v <PATH_TO_PICUTRES_DIR>:/opt/Pictures \
  -v <PATH_TO_CONFIG_DIR>/minidlna.conf:/etc/minidlna.conf \
  geekduck/minidlna

docker-minidlna's Issues

inotify doesn't work on NFS volumes

Need a way to force a refresh as inotify doesn't work if we're using NFS to store the media

eg

podman volume create --opt type=nfs --opt o=ro --opt device=mediaserver:/mnt/Videos Videos

podman run -d --name minidlna \
  --net=host \
  -v Video:/opt/Videos \
  -v /var/cache/minidlna:/var/cache/minidlna:Z \
  geekduck/minidlna

Is there any way to get a refresh without reloading/rebuilding the DB. I'm running with a persistent Cache and DB. Start/Stop doesn't cause a re-scan

podman stop minidlna
podman start minidlna

-d parameter means debug not daemonize

You should not use -d but -S to run the process in foreground.

Using -d will mean slower performance and a lot of logs (really a lot of logs).

Error message "Inotify max_user_watches"

Sometimes I'm getting the error message:
monitor.c:216: warn: WARNING: Inotify max_user_watches [8192] is low or close to the number of used watches [2451] 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
Afterwards the docker is stopped with minidlna.c:155: warn: received signal 15, good-bye

Is there a possibility to increase the value?

Exposing port is not necessary

Do you really have to expose ports using "-p" in docker run? You are using net=host, I think this would be unnecessary. Can you confirm?

MiniDLNA is already running

Since recently the container stopped working without me changing any settings. It crashes on start right away stating:

minidlna.c:961: error: MiniDLNA is already running. EXITING.

Network mode Exposed Ports

While in network mode, it's moot to append the ports to use as well in the docker command/compose since it's already in host mode. It runs fine as is, but it gives the misconception of what host mode is and that those port variables are required.