{"id":13465960,"url":"https://github.com/romancin/tinymediamanager-docker","last_synced_at":"2026-02-04T21:41:05.132Z","repository":{"id":46229663,"uuid":"143615645","full_name":"romancin/tinymediamanager-docker","owner":"romancin","description":"A repository for creating a docker container including TinyMediaManager with GUI interface.","archived":false,"fork":false,"pushed_at":"2023-02-16T10:53:36.000Z","size":58,"stargazers_count":220,"open_issues_count":26,"forks_count":73,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-03-25T21:35:25.561Z","etag":null,"topics":["docker","docker-image","hacktoberfest"],"latest_commit_sha":null,"homepage":"","language":"Dockerfile","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/romancin.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2018-08-05T13:35:35.000Z","updated_at":"2025-03-24T12:16:49.000Z","dependencies_parsed_at":"2024-01-13T17:59:33.470Z","dependency_job_id":"a9729646-72bb-4202-8399-a2d165ec7f53","html_url":"https://github.com/romancin/tinymediamanager-docker","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/romancin/tinymediamanager-docker","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/romancin%2Ftinymediamanager-docker","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/romancin%2Ftinymediamanager-docker/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/romancin%2Ftinymediamanager-docker/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/romancin%2Ftinymediamanager-docker/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/romancin","download_url":"https://codeload.github.com/romancin/tinymediamanager-docker/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/romancin%2Ftinymediamanager-docker/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29096532,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-04T21:05:08.033Z","status":"ssl_error","status_checked_at":"2026-02-04T21:04:53.031Z","response_time":62,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["docker","docker-image","hacktoberfest"],"created_at":"2024-07-31T15:00:37.350Z","updated_at":"2026-02-04T21:41:05.100Z","avatar_url":"https://github.com/romancin.png","language":"Dockerfile","funding_links":["https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick\u0026hosted_button_id=X2CT2SWQCP74U"],"categories":["Dockerfile"],"sub_categories":[],"readme":"# tinymediamanager-docker\n\nA repository for creating a docker container including TinyMediaManager with GUI interface.\n\n![docker pulls](https://img.shields.io/docker/pulls/romancin/tinymediamanager.svg) ![docker stars](https://img.shields.io/docker/stars/romancin/tinymediamanager.svg) [![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick\u0026hosted_button_id=X2CT2SWQCP74U)\n\nLatest versions:\n\n![Docker Image Version (latest semver)](https://img.shields.io/docker/v/romancin/tinymediamanager/v4) ![docker size](https://img.shields.io/docker/image-size/romancin/tinymediamanager/v4) \n\n![Docker Image Version (tag latest semver)](https://img.shields.io/docker/v/romancin/tinymediamanager/v3) ![docker size](https://img.shields.io/docker/image-size/romancin/tinymediamanager/v3) \n\n\nIf you are migrating from v3 to v4, please make a backup before. I recommend you create a new host directory to map the new config, and copy the \"/config/data\" folder from v3 version to it.\nTake a look at the official upgrade documentation here:\nhttps://www.tinymediamanager.org/docs/upgrade-v4\n\nYou can invite me a beer if you want ;) \n\nThis is a completely funcional Docker image with TinyMediaManager.\n\nBased on Alpine Linux, which provides a very small size. \n\nTested and working on Synology and QNAP, but should work on any x86_64 devices.\n\nThanks to @jlesage for a great base image for GUI apps.\n\nInstructions: \n- Map any local port to 5800 for web access\n- Map any local port to 5900 for VNC access\n- Map a local volume to /config (Stores configuration data)\n- Map a local volume to /media (Access media files)\n\nSample run command:\n\n```bash\ndocker run -d --name=tinymediamanager \\\n-v /share/Container/tinymediamanager/config:/config \\\n-v /share/Container/tinymediamanager/media:/media \\\n-e GROUP_ID=0 -e USER_ID=0 -e TZ=Europe/Madrid \\\n-p 5800:5800 \\\n-p 5900:5900 \\\nromancin/tinymediamanager:latest-v4\n```\n\nBrowse to `http://your-host-ip:5800` to access the TinyMediaManager GUI.\n\n### Image TAGs available\n\n| TAG       | Description                                  |\n|-----------|----------------------------------------------|\n|`latest`| Latest available version of **TMM v3** |\n|`latest-v4`| Latest available version of **TMM v4** |\n|`vX.X.X` | Points directly to one of the TMM versions available, v3 or v4 |\n\n### Environment Variables\n\nTo customize some properties of the container, the following environment\nvariables can be passed via the `-e` parameter (one for each variable).  Value\nof this parameter has the format `\u003cVARIABLE_NAME\u003e=\u003cVALUE\u003e`.\n\n| Variable       | Description                                  | Default |\n|----------------|----------------------------------------------|---------|\n|`USER_ID`| ID of the user the application runs as.  See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`GROUP_ID`| ID of the group the application runs as.  See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`SUP_GROUP_IDS`| Comma-separated list of supplementary group IDs of the application. | (unset) |\n|`UMASK`| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation.  By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) |\n|`TZ`| [TimeZone] of the container.  Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Etc/UTC` |\n|`KEEP_APP_RUNNING`| When set to `1`, the application will be automatically restarted if it crashes or if user quits it. | `0` |\n|`APP_NICENESS`| Priority at which the application should run.  A niceness value of -20 is the highest priority and 19 is the lowest priority.  By default, niceness is not set, meaning that the default niceness of 0 is used.  **NOTE**: A negative niceness (priority increase) requires additional permissions.  In this case, the container should be run with the docker option `--cap-add=SYS_NICE`. | (unset) |\n|`CLEAN_TMP_DIR`| When set to `1`, all files in the `/tmp` directory are delete during the container startup. | `1` |\n|`DISPLAY_WIDTH`| Width (in pixels) of the application's window. | `1280` |\n|`DISPLAY_HEIGHT`| Height (in pixels) of the application's window. | `768` |\n|`SECURE_CONNECTION`| When set to `1`, an encrypted connection is used to access the application's GUI (either via web browser or VNC client).  See the [Security](#security) section for more details. | `0` |\n|`VNC_PASSWORD`| Password needed to connect to the application's GUI.  See the [VNC Password](#vnc-password) section for more details. | (unset) |\n|`X11VNC_EXTRA_OPTS`| Extra options to pass to the x11vnc server running in the Docker container.  **WARNING**: For advanced users. Do not use unless you know what you are doing. | (unset) |\n|`ENABLE_CJK_FONT`| When set to `1`, open source computer font `WenQuanYi Zen Hei` is installed.  This font contains a large range of Chinese/Japanese/Korean characters. | `0` |\n\n### Data Volumes\n\nThe following table describes data volumes used by the container.  The mappings\nare set via the `-v` parameter.  Each mapping is specified with the following\nformat: `\u003cHOST_DIR\u003e:\u003cCONTAINER_DIR\u003e[:PERMISSIONS]`.\n\n| Container path  | Permissions | Description |\n|-----------------|-------------|-------------|\n|`/config`| rw | This is where the application stores its configuration, log and any files needing persistency. |\n|`/media`| rw | This is where your media files are stored. |\n\n### Ports\n\nHere is the list of ports used by the container.  They can be mapped to the host\nvia the `-p` parameter (one per port mapping).  Each mapping is defined in the\nfollowing format: `\u003cHOST_PORT\u003e:\u003cCONTAINER_PORT\u003e`.  The port number inside the\ncontainer cannot be changed, but you are free to use any port on the host side.\n\n| Port | Mapping to host | Description |\n|------|-----------------|-------------|\n| 5800 | Mandatory | Port used to access the application's GUI via the web interface. |\n| 5900 | Optional | Port used to access the application's GUI via the VNC protocol.  Optional if no VNC client is used. |\n\n## User/Group IDs\n\nWhen using data volumes (`-v` flags), permissions issues can occur between the\nhost and the container.  For example, the user within the container may not\nexists on the host.  This could prevent the host from properly accessing files\nand folders on the shared volume.\n\nTo avoid any problem, you can specify the user the application should run as.\n\nThis is done by passing the user ID and group ID to the container via the\n`USER_ID` and `GROUP_ID` environment variables.\n\nTo find the right IDs to use, issue the following command on the host, with the\nuser owning the data volume on the host:\n\n    id \u003cusername\u003e\n\nWhich gives an output like this one:\n```\nuid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)\n```\n\nThe value of `uid` (user ID) and `gid` (group ID) are the ones that you should\nbe given the container.\n\n## Security\n\nBy default, access to the application's GUI is done over an unencrypted\nconnection (HTTP or VNC).\n\nSecure connection can be enabled via the `SECURE_CONNECTION` environment\nvariable.  See the [Environment Variables](#environment-variables) section for\nmore details on how to set an environment variable.\n\nWhen enabled, application's GUI is performed over an HTTPs connection when\naccessed with a browser.  All HTTP accesses are automatically redirected to\nHTTPs.\n\nWhen using a VNC client, the VNC connection is performed over SSL.  Note that\nfew VNC clients support this method.  [SSVNC] is one of them.\n\n[SSVNC]: http://www.karlrunge.com/x11vnc/ssvnc.html\n\n### Certificates\n\nHere are the certificate files needed by the container.  By default, when they\nare missing, self-signed certificates are generated and used.  All files have\nPEM encoded, x509 certificates.\n\n| Container Path                  | Purpose                    | Content |\n|---------------------------------|----------------------------|---------|\n|`/config/certs/vnc-server.pem`   |VNC connection encryption.  |VNC server's private key and certificate, bundled with any root and intermediate certificates.|\n|`/config/certs/web-privkey.pem`  |HTTPs connection encryption.|Web server's private key.|\n|`/config/certs/web-fullchain.pem`|HTTPs connection encryption.|Web server's certificate, bundled with any root and intermediate certificates.|\n\n**NOTE**: To prevent any certificate validity warnings/errors from the browser\nor VNC client, make sure to supply your own valid certificates.\n\n**NOTE**: Certificate files are monitored and relevant daemons are automatically\nrestarted when changes are detected.\n\n### VNC Password\n\nTo restrict access to your application, a password can be specified.  This can\nbe done via two methods:\n  * By using the `VNC_PASSWORD` environment variable.\n  * By creating a `.vncpass_clear` file at the root of the `/config` volume.\n    This file should contains the password in clear-text.  During the container\n    startup, content of the file is obfuscated and moved to `.vncpass`.\n\nThe level of security provided by the VNC password depends on two things:\n  * The type of communication channel (encrypted/unencrypted).\n  * How secure access to the host is.\n\nWhen using a VNC password, it is highly desirable to enable the secure\nconnection to prevent sending the password in clear over an unencrypted channel.\n\n**ATTENTION**: Password is limited to 8 characters.  This limitation comes from\nthe Remote Framebuffer Protocol [RFC](https://tools.ietf.org/html/rfc6143) (see\nsection [7.2.2](https://tools.ietf.org/html/rfc6143#section-7.2.2)).  Any\ncharacters beyhond the limit are ignored.\n\n## Shell Access\n\nTo get shell access to a the running container, execute the following command:\n\n```\ndocker exec -ti CONTAINER sh\n```\n\nWhere `CONTAINER` is the ID or the name of the container used during its\ncreation (e.g. `crashplan-pro`).\n\n## Reverse Proxy\n\nThe following sections contains NGINX configuration that need to be added in\norder to reverse proxy to this container.\n\nA reverse proxy server can route HTTP requests based on the hostname or the URL\npath.\n\n### Routing Based on Hostname\n\nIn this scenario, each hostname is routed to a different application/container.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container.  The server would proxy all HTTP requests sent to\n`tinymediamanager.domain.tld` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t''      close;\n}\n\nupstream tinymediamanager {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tserver_name tinymediamanager.domain.tld;\n\n\tlocation / {\n\t        proxy_pass http://tinymediamanager;\n\t}\n\n\tlocation /websockify {\n\t\tproxy_pass http://tinymediamanager;\n\t\tproxy_http_version 1.1;\n\t\tproxy_set_header Upgrade $http_upgrade;\n\t\tproxy_set_header Connection $connection_upgrade;\n\t\tproxy_read_timeout 86400;\n\t}\n}\n\n```\n\n### Routing Based on URL Path\n\nIn this scenario, the hostname is the same, but different URL paths are used to\nroute to different applications/containers.\n\nFor example, let's say the reverse proxy server is running on the same machine\nas this container.  The server would proxy all HTTP requests for\n`server.domain.tld/tinymediamanager` to the container at `127.0.0.1:5800`.\n\nHere are the relevant configuration elements that would be added to the NGINX\nconfiguration:\n\n```\nmap $http_upgrade $connection_upgrade {\n\tdefault upgrade;\n\t''      close;\n}\n\nupstream tinymediamanager {\n\t# If the reverse proxy server is not running on the same machine as the\n\t# Docker container, use the IP of the Docker host here.\n\t# Make sure to adjust the port according to how port 5800 of the\n\t# container has been mapped on the host.\n\tserver 127.0.0.1:5800;\n}\n\nserver {\n\t[...]\n\n\tlocation = /tinymediamanager {return 301 $scheme://$http_host/tinymediamanager/;}\n\tlocation /tinymediamanager/ {\n\t\tproxy_pass http://tinymediamanager/;\n\t\tlocation /tinymediamanager/websockify {\n\t\t\tproxy_pass http://tinymediamanager/websockify/;\n\t\t\tproxy_http_version 1.1;\n\t\t\tproxy_set_header Upgrade $http_upgrade;\n\t\t\tproxy_set_header Connection $connection_upgrade;\n\t\t\tproxy_read_timeout 86400;\n\t\t}\n\t}\n}\n\n```\n\n[TimeZone]: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones\n\n## Support or Contact\n\nHaving troubles with the container or have questions?  Please\n[create a new issue].\n\n## Changelog\n\nv4.1.1 (16/03/2021): First version of TMM v4 (v4.1.1)\n\nv3.1.10 (31/10/2020): Updated TMM to 3.1.10\n\nv3.1.8 (09/09/2020): Updated to latest image from jlesage for Alpine 3.12, updated Corretto to current 1.8 version and TMM to 3.1.8\n\nv1.0.1 (22/09/2019): Updated to latest image from jlesage and added Jenkinsfile for CI\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fromancin%2Ftinymediamanager-docker","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fromancin%2Ftinymediamanager-docker","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fromancin%2Ftinymediamanager-docker/lists"}