Closed matthiasklabe closed 9 months ago
I'm using Debian bookworm at an AMD64 Server with Docker 25.0.0
Hello, looks like a permission issue, can you post your compose file?
version: "3"
services: minidlna-desktop: image: giof71/minidlna container_name: minidlna network_mode: host user: "1000:1000" environment:
Ok, can you please post the output of
id
Assuming it will be 1000:1000, I believe you should do:
docker-compose down
sudo chown -R 1000:1000 ./config
docker-compose up -d
Let me know if this helps
THX for fast reply. I started this stack with portainer and I have some other stacks running as well.
docker-compose.yml will be used several times for the other stacks as well.
docker-compose down is not working in ssh console.
Sorry I'm a "newbee" in this topic.
Which error do you get when running docker-compose down? I think you might have not installed docker-compose. You can install it using
sudo apt-get install docker-compose
Ok if you are using Portainer, these "./config/..." paths won't work and/or are not the best idea. You need absolute paths. Anyway if you want to use portainer, I would start dropping the line that says:
user: "1000:1000"
and would instead add the two variables:
PUID=1000
PGID=1000
I would create two volumes, named e.g. minidlna_db and minidlna_log and I would map those to /db and /log respectively, using the GUI. But in order to make things simple, you can try first without any mounted directory for /db and /tmp
Let me know if this helps
Sorry also add variable:
USER_MODE=Y
so that you can eventually deny it easily
Hi, volume is working, but container is restarting... you can see console and portainer log in the background.
I don't see the final part of the log... and I cannot open the image, can you post the text? The part you highlighted is ok, the script is changing the permissions on the volumes (it can do that because it is not run in docker user mode)
This is the log which I copied out of portainer:
Current user id is [0] t=A Processing media_dir for ENV_NAME=[/music/library1] t=P Processing media_dir for ENV_NAME=[] t=V Processing media_dir for ENV_NAME=[] t=A Processing media_dir for ENV_NAME=[/music/library2] t=P Processing media_dir for ENV_NAME=[] t=V Processing media_dir for ENV_NAME=[] t=A Processing media_dir for ENV_NAME=[/music/library3] t=P Processing media_dir for ENV_NAME=[] t=V Processing media_dir for ENV_NAME=[] t=A Processing media_dir for ENV_NAME=[] t=P Processing media_dir for ENV_NAME=[] t=V Processing media_dir for ENV_NAME=[] t=A Processing media_dir for ENV_NAME=[] t=P Processing media_dir for ENV_NAME=[] t=V Processing media_dir for ENV_NAME=[] group minidlna-user already exists. user minidlna-user already exists. Setting user permissions on /log ... Setting user permissions on /db ... User permissions set.
and then it restarts. In other cases the ports causes issues, but the host has no used ports
sorry for the copy paste issue... no idea where it came from. Really appreciated your effort to help me!
do the paths:
/mnt/disk1/library /mnt/disk2/library /mnt/disk3/library
actually exist? they look the same I provided as an example. You need to tune those values to your actual paths
Which directory/directories do you want to serve with minidlna?
minidlna-log from Volumê
you could be right to serve special dirctories, but I thought this is generic setup
Do you have any other instance of minidlna running? maybe as a package on the host system?
try:
ps aux | grep minidlna
you could be right to serve special dirctories, but I thought this is generic setup
yes but I cannot know which will be the path(s) you want to share... only you know that, which names you gave to your media directories, etc. You need to provide that/those paths
Maybe I need to clarify this in the readme file.
Those paths have been create now in your filesystem although they are probably empty, you can clean those by:
sudo rmdir /mnt/disk1/library /mnt/disk2/library /mnt/disk3/library
those look like errors when network_mode is not host. Are you still using the compose file or manipulating the container using portainer?
I'm using compose file which is still in my private gitlab. In portainer I'm using "pull and re-deploy"
do you see other minidlna containers active in portainer?
Let's get these path correct first then we see if the errors persist. Can you tell me the full path of the media files you want to share?
There is nothing to share right now, but I will put something into /var/lib/docker/volumes/music1/_data....this is clear so far. It should only work for the little kid. Around 20 songs ;-) Later I want to use it by myself a bit more.
To answer your question, there is no minidlna container running
try removing that restart: unless-stopped
, and re-create the container
it starts and it stopped after some time
ok so can you post the last log?
is any container possibly using port 8200?
I don't know where you from, but I don't want you to spend your "night" for my problem. I'm from Germany and it is around 7 p.m.
maybe the port need to be add into the docker-compose.yml?
I didn't even make it configurable... yet. But as long as there is no conflict, I think that is not the issue. Seeing the log I noticed this:
No such file or directory
Have you corrected the mount points?
No worries, we're on the same TZ, I'm from Italy I don't see 8200 in that list, am I wrong? Plot tickens
yes there is no 3200, maybe it need to add in YML
Seeing the log I noticed this:
No such file or directory
Have you corrected the mount points for the libraries?
If you mean /run/minssdpd - NO. I dont know why this need to be there... I started from scratch with headless DEBIAN bookworm. Then installed some additionals like "net-tools" and "mc". Then Installes Docker.io 25.0.0 and went forward with partainer and adding stacks out of my private gitlab.
I found out, right away, that this is needed in the host to provide DLNA from Host
I istalled it at my docker host an will let you know
No I mean the paths for your files. Let's try starting simple. I assume you want to share music but if not, replace "A" with "V". Simpler docker-compose file:
---
version: "3"
services:
minidlna-desktop:
image: giof71/minidlna
container_name: minidlna
network_mode: host
environment:
- USER_MODE=Y
- PUID=1000
- PGID=1000
- MINIDLNA_ROOT_CONTAINER=M
- MINIDLNA_DIR_A_1=/music/library1
- MINIDLNA_ENABLE_INOTIFY=YES
- MINIDLNA_FRIENDLY_NAME=minidlna
- MINIDLNA_FORCE_SORT_CRITERIA=+upnp:class,-dc:date,+upnp:album,+upnp:originalTrackNumber,+dc:title
volumes:
- /path/to/music:/music/library1
I istalled it at my docker host an will let you know
So did you solve it?
unfortunately not. I used "sudo apt get install minissdpd" an rebooted the system. Service is now running at the host and missing file is also there
after a second restart, minissdpd does not come up proper and .sock file is also disapeared. As mentioned I'm expecting this "minissdpd" in the container. Anyways - take your time to investigate - no stress ;-)
I never experienced this... I am currently clueless. Can you try this other minidlna docker container and see if this one works?
to be honest I tried it before as well, with same result
uhm ok, that's encouraging at least :-)
Could be that it is related to bookworm 64 bit, but I don't want to downgrade.
I can't exclude it... the server I am running it on is bullseye, but with that I am not encouraging to downgrade of course (I wouldn't)
IF you find the solution and send me you paypal, I will spend some money ;-)
Thank you, no it won't be necessary, but thank you anyway
Hello, if you install minidlna on the host machine, does it work properly? Thank you
Hi,
If I use your image and deploy the stack in portainer I get this error message in the log files of the container
"minidlna.c:1028: fatal: Failed to open log file '/log/minidlna.log': Permission denied"
could you please check and advise ?
THX Matthias