[{"_1":2,"_156":-5,"_157":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_135":136},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_85":-5,"_86":87,"_126":-5,"_127":11,"_128":17,"_129":11,"_130":-5,"_131":11,"_132":-5,"_133":134},"canonicalUrl","https://hub.docker.com/r/arranhs/filebot/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","arranhs","reponame","filebot","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":71,"_76":11,"_77":78,"_82":29,"_83":84},"categories",[],"content_types",[40],"image","date_registered","2019-09-07T03:48:12.014955Z","description","Docker container for FileBot using Guacamole to allow browser access","is_private","last_updated","2019-12-06T13:41:19.055404Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",734079,"repository_type","star_count",3,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# Docker container for FileBot\n\nThis is a Docker container for FileBot. Much of the work came from jlesage's excellent filebot image but this image ustilises Guacamole due to its advantages. \n\nThe GUI of the application is accessed through a modern web browser (no installation or configuration needed on client side) or via any VNC client. \n\n**Guacamole** is used for GUI access in this fork. This is different to jlesage's image, and means the viewer will be more performant.\n\n**This container uses FileBot version 4.7.9 as this is the last free version available.** \n**While the container will be updated, the FileBot version will not be.**\n\n---\n\n[![FileBot logo](https://images.weserv.nl/?url=raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/filebot-icon.png&w=200)](http://www.filebot.net/)[![FileBot](https://dummyimage.com/400x110/ffffff/575757&text=FileBot)](http://www.filebot.net/)\n\nFileBot is the ultimate tool for organizing and renaming your movies, tv shows\nor anime, and music well as downloading subtitles and artwork. It's smart and\njust works.\n\n---\n\n## Table of Content\n\n * [Docker container for FileBot](#docker-container-for-filebot)\n * [Table of Content](#table-of-content)\n * [Quick Start](#quick-start)\n * [Usage](#usage)\n * [Environment Variables](#environment-variables)\n * [Data Volumes](#data-volumes)\n * [Ports](#ports)\n * [Changing Parameters of a Running Container](#changing-parameters-of-a-running-container)\n * [Docker Image Update](#docker-image-update)\n * [User/Group IDs](#usergroup-ids)\n * [Accessing the GUI](#accessing-the-gui)\n * [Shell Access](#shell-access)\n * [Support or Contact](#support-or-contact)\n\n## Quick Start\n\n**NOTE**: The Docker command provided in this quick start is given as an example\nand parameters should be adjusted to your need.\n\nLaunch the FileBot docker container with the following command:\n```\ndocker run -d \\\n --name=filebot \\\n -p 8080:8080 \\\n -v /docker/appdata/filebot:/config \\\n -v $HOME:/storage \\\n arranhs/filebot\n```\n\nWhere:\n - `/docker/appdata/filebot`: This is where the application stores its configuration, log and any files needing persistency.\n - `$HOME`: This location contains files from your host that need to be accessible by the application.\n\nBrowse to `http://your-host-ip:8080` to access the FileBot GUI.\nFiles from the host appear under the `/storage` folder in the container.\n\n## Usage\n\n```\ndocker run [-d] \\\n --name=filebot \\\n [-e =]... \\\n [-v :[:PERMISSIONS]]... \\\n [-p :]... \\\n arranhs/filebot\n```\n| Parameter | Description |\n| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| -d | Run the container in background. If not set, the container runs in foreground. |\n| -e | Pass an environment variable to the container. See the [Environment Variables](#environment-variables) section for more details. |\n| -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the [Data Volumes](#data-volumes) section for more details. |\n| -p | Set a network port mapping (exposes an internal container port to the host). See the [Ports](#ports) section for more details. |\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 `=`.\n\n| Variable | Description | Default |\n| -------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------- |\n| `UID` | ID of the user the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n| `GID` | ID of the group the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n| `TZ` | [TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Europe/London` |\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: `:[: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| `/storage` | rw | This location contains files from your host that need to be accessible by the application. |\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: `:`. 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| 8080 | Mandatory | Port used to access the application's GUI via the web interface. |\n| 3389 | Optional | Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used. |\n\n### Changing Parameters of a Running Container\n\nAs seen, environment variables, volume mappings and port mappings are specified\nwhile creating the container.\n\nThe following steps describe the method used to add, remove or update\nparameter(s) of an existing container. The generic idea is to destroy and\nre-create the container:\n\n 1. Stop the container (if it is running):\n```\ndocker stop filebot\n```\n 2. Remove the container:\n```\ndocker rm filebot\n```\n 3. Create/start the container using the `docker run` command, by adjusting\n parameters as needed.\n\n**NOTE**: Since all application's data is saved under the `/config` container\nfolder, destroying and re-creating a container is not a problem: nothing is lost\nand the application comes back with the same state (as long as the mapping of\nthe `/config` folder remains the same).\n\n## Docker Image Update\n\nIf the system on which the container runs doesn't provide a way to easily update\nthe Docker image, the following steps can be followed:\n\n 1. Fetch the latest image:\n```\ndocker pull arranhs/filebot\n```\n 2. Stop the container:\n```\ndocker stop filebot\n```\n 3. Remove the container:\n```\ndocker rm filebot\n```\n 4. Start the container using the `docker run` command.\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`UID` and `GID` 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 \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## Accessing the GUI\n\nAssuming that container's ports are mapped to the same host's ports, the\ngraphical interface of the application can be accessed via:\n\n * A web browser:\n```\nhttp://:8080\n```\n\n * Any VNC client:\n```\n:3389\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. `filebot`).\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[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[create a new issue]: https://github.com/ahobsonsayers/docker-filebot/issues\n","has_starred","hub_user","immutable_tags_settings",{"_72":11,"_73":74},"enabled","rules",[75],".*","is_automated","permissions",{"_79":17,"_80":11,"_81":11},"read","write","admin","user","storage_size",1310356677,"orgData","recentTags",[88],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":97,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},"content_type","creator",2489527,"full_size",516418704,"id",68211095,"images",[98],{"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":110,"_111":104,"_112":-5,"_113":93,"_59":62,"_114":-5},"architecture","amd64","digest","sha256:07d070f5ec3c5123b9d15fc6be616e42598a55efbb477641cbf8f76e60524c5e","features","","last_pulled","2026-09-26T18:21:05.32404928Z","last_pushed","2019-12-06T13:41:19Z","os","linux","os_features","os_version","size","variant","2019-12-06T13:41:18.749706Z","last_updater","last_updater_username","media_type","latest","repository",7664199,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":137,"_144":145,"_133":154,"_155":11},{"_36":138,"_38":139,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":140,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":141,"_76":11,"_77":143,"_82":29,"_83":84},[],[40],[52],{"_72":11,"_73":142},[75],{"_79":17,"_80":11,"_81":11},"tags",{"_146":60,"_147":-5,"_148":-5,"_149":150},"count","next","previous","results",[151],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":152,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},[153],{"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":110,"_111":104,"_112":-5,"_113":93,"_59":62,"_114":-5},[],"canDeleteTags","actionData","errors"]

arranhs/filebot

Tags for arranhs/filebot