![]() ![]() /data: where all local data of tinyMediaManager will be stores.You should map the following folders to a volume/folder on the host: E.g.:ĭocker run \ -name =tinymediamanager \ -p 4000:4000 \ -v :/data \ -v :/media/movies \ -v :/media/tvshows \Īfter starting the container, you can access tinyMediaManager via Data volumes Map local volumes/folders/mounts to /media/xxx where all media will be accessed.Map a local volume/folder to /data where all local data from tinyMediaManager is stores (like data, logs, cache and backups).Map any local port to 4000 for web access (via noVNC).Using this image, you will get a fully working instance of tinyMediaManager which is accessible remotely (via web/VNC). This image should work on any x86_64 device. This image includes all needed components (up to date libmediainfo, FFmpeg, …) for the best experience. TinyMediaManager offers an (experimental) official docker image based on Debian Buster (for maximum compatibility). Solve the problem of audio tracks being of ‘unknown language’.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |