[minidlna] /minidlna/cache/files.db on persistent volume about docker_base_images

[accountForIssues]

Are you sure the database is recreated at every start ?

I posted my docker-compose in #108 and have been using it since a long time. I'm pretty sure it doesn't rebuild at every start.

There are times where minidlna doesn't pickup new files, then I just execute this command to do the soft-rescan.
docker exec -it minidlna minidlnad -r

The container doesn't need to be started or stopped and minidlna picks up the new files almost instantly.

[n00ris]

Hi @accountForIssues . Thank you for your idea. Maybe you got me wrong:
I am not speaking about restart / reboot.
I'm intereseted in a smooth update procedure.
I re-created the container to update the container itself to the latest version
(high level procedure: pull latest image, delete container, start ne container with new image, keep volumes).
Result: An update is similar to setup a very new container, you just keep data on your persistent volumes/bind mounts.

[accountForIssues]

Okay, well using the docker-compose will let you do that.

I assume you were talking about the docker run command given in the README where there is a loss of data upon updating ? If so, that's what I was afraid as well and hence just went the compose route to write data to disk.

[vladgh]

I am not quite sure I understand what the issue is, but I think this is intended behavior. The container does not mount any volumes, and no data is preserved between runs. Unless you specify runtime volumes that you want to keep (cache, settings, etc.). And in that case, @accountForIssues is perfectly right, you can docker exec the desired rescan commands into the running container.

[n00ris]

Sorry for the long time to respond. Let me explain my use case.
Minidlna is running on a NAS with Openmediavault.
Some of the users may not be skilled linux users.
Ask them to run a docker exec -it minidlna minidlnad -r would be impossible...

So portainer is used as a GUI to docker. I was looking for a way to update the database with the portainer UI.
And other docker image provider may provide a ENV variable to enable update on reboot, instead of a re-create.
If you can provide a "minidlnad -r" run on boot that would be sufficient (My idea of an ENV variable just make it configurable).

After that, I can just tell the others to reboot the whole NAS (or the container via portainer) and check if the files became visible...

[vladgh]

Okay, I don't see why that would hurt. I will work on it in the next few days.

[vladgh]

Okay, I don't see why that would hurt. I will work on it in the next few days.

And then Hurricane Ida hit my city, New Orleans!

But now I added 2 options to the environment:

• FORCE_SCAN=true will start with -r, which forces a rescan
• FORCE_REBUILD=true will start with -R, which forces a rebuild of the database

I hope that helps. If you want to test it, use the vladgh/minidlna:sha-d3ba2bc tag, but it should be merged and I will create a new release very soon.

[vladgh]

Release v1.2.0 is published

docker pull vladgh/minidlna:1.2

[n00ris]

And then Hurricane Ida hit my city, New Orleans!

Oh wow, I hope you and your family are doing well.

But now I added 2 options to the environment:
Thank you! It looks very much I was looking for. I really appreciate that very much.

I will check it out.