Docker Request

[C4Wiz]

could you create a docker for tiny media manager v4?

[jlesage]

Yes it could be possible.
But I see that there is an official one: https://hub.docker.com/r/tinymediamanager/tinymediamanager. Did you try it? Or you would prefer something based on Alpine and with the web interface of this base image ?

[C4Wiz]

i prefer alpine

[C4Wiz]

i got it going here: https://github.com/C4Wiz/tinymediamanager4-docker

no clue if it's correct

[jlesage]

There is also this one, which uses my base image: https://hub.docker.com/r/romancin/tinymediamanager

[jlesage]

FYI, it would be harder make a "clean" Docker container for tinyMediaManager, because of this: https://gitlab.com/tinyMediaManager/tinyMediaManager/-/issues/1706

[C4Wiz]

FYI, it would be harder make a "clean" Docker container for tinyMediaManager, because of this: https://gitlab.com/tinyMediaManager/tinyMediaManager/-/issues/1706

i got it working perfectly using the debian 11 base image: https://github.com/C4Wiz/tinymediamanager4-docker

[jlesage]

It's working because the whole software is running from /config, instead of being part of the image.

[C4Wiz]

It's working because the whole software is running from /config, instead of being part of the image.

TMM has always been a self contained app so to speak, it's portable.

my config directory is on a nvme ssd anyway.

is it not possible to make the image r/w?

[jlesage]

Well everything written to the image is lost when the container is re-created (e.g. when updating the image or when changing the container config).

So I personally like to make sure the implemented application write all needed data to /config. I also try to prevent softwares to do self-update, since this can easily break the container. I prefer to provide a new image every time there is a new software update.

[the-hotmann]

i prefer alpine

Then change this line: https://github.com/C4Wiz/tinymediamanager4-docker/blob/main/Dockerfile#L4

to: FROM jlesage/baseimage-gui:alpine-3.15 or FROM jlesage/baseimage-gui:alpine-3.15-glibc and install all the dependencies yourself.

After that mount persistent storage into your container, so that the file you work with and the config will not be lost if you re-create/update your container.