[{"_1":2,"_162":-5,"_163":-5},"loaderData",{"_3":4,"_13":14,"_20":21,"_137":138},"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},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","routes/_layout.r.$namespace.$reponame",{"_22":23,"_24":-5,"_25":11,"_26":11,"_27":28,"_29":30,"_31":-5,"_32":11,"_33":34,"_83":-5,"_84":85,"_130":-5,"_131":11,"_132":17,"_133":11,"_134":-5,"_135":136},"canonicalUrl","https://hub.docker.com/r/dismantl/docker-makemkv/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","dismantl","reponame","docker-makemkv","cloudBuildSource","isAutobuildsAvailable","repo",{"_35":36,"_37":38,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":50,"_52":30,"_27":28,"_53":54,"_55":39,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":69,"_74":17,"_75":76,"_80":28,"_81":82},"categories",[],"content_types",[39],"image","date_registered","2018-08-18T21:51:35.150586Z","description","for pull request","is_private","last_updated","2018-08-18T22:38:14.270301Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[51],"application/vnd.docker.container.image.v1+json","name","pull_count",536,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Docker container for MakeMKV\n[![Docker Automated build](https://img.shields.io/docker/automated/jlesage/makemkv.svg)](https://hub.docker.com/r/jlesage/makemkv/) [![Docker Image](https://images.microbadger.com/badges/image/jlesage/makemkv.svg)](http://microbadger.com/#/images/jlesage/makemkv) [![Build Status](https://travis-ci.org/jlesage/docker-makemkv.svg?branch=master)](https://travis-ci.org/jlesage/docker-makemkv) [![GitHub Release](https://img.shields.io/github/release/jlesage/docker-makemkv.svg)](https://github.com/jlesage/docker-makemkv/releases/latest) [![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://paypal.me/JocelynLeSage/0usd)\n\nThis is a Docker container for MakeMKV.\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\nA fully automated mode is also available: insert a DVD or Blu-ray disc into an optical drive and let MakeMKV rips it without any user interaction.\n\n---\n\n[![MakeMKV logo](https://images.weserv.nl/?url=raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/makemkv-icon.png&w=200)](http://www.makemkv.com/)[![MakeMKV](https://dummyimage.com/400x110/ffffff/575757&text=MakeMKV)](http://www.makemkv.com/)\n\nMakeMKV is your one-click solution to convert video that you own into free and\npatents-unencumbered format that can be played everywhere. MakeMKV is a format\nconverter, otherwise called \"transcoder\". It converts the video clips from\nproprietary (and usually encrypted) disc into a set of MKV files, preserving\nmost information but not changing it in any way. The MKV format can store\nmultiple video/audio tracks with all meta-information and preserve chapters.\n\n---\n\n## Table of Content\n\n * [Docker container for MakeMKV](#docker-container-for-makemkv)\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 Compose File](#docker-compose-file)\n * [Docker Image Update](#docker-image-update)\n * [Synology](#synology)\n * [unRAID](#unraid)\n * [User/Group IDs](#usergroup-ids)\n * [Accessing the GUI](#accessing-the-gui)\n * [Security](#security)\n * [Certificates](#certificates)\n * [VNC Password](#vnc-password)\n * [Shell Access](#shell-access)\n * [Reverse Proxy](#reverse-proxy)\n * [Routing Based on Hostname](#routing-based-on-hostname)\n * [Routing Based on URL Path](#routing-based-on-url-path)\n * [Access to Optical Drive(s)](#access-to-optical-drives)\n * [Automatic Disc Ripper](#automatic-disc-ripper)\n * [Troubleshooting](#troubleshooting)\n * [Expired Beta Key](#expired-beta-key)\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 MakeMKV docker container with the following command:\n```\ndocker run -d \\\n --name=makemkv \\\n -p 5800:5800 \\\n -v /docker/appdata/makemkv:/config:rw \\\n -v $HOME:/storage:ro \\\n -v $HOME/MakeMKV/output:/output:rw \\\n --device /dev/sr0 \\\n --device /dev/sg2 \\\n jlesage/makemkv\n```\n\nWhere:\n - `/docker/appdata/makemkv`: 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 - `$HOME/MakeMKV/output`: This is where extracted videos are written.\n - `/dev/sr0`: This is the first Linux device file representing the optical drive.\n - `/dev/sg2`: This is the second Linux device file representing the optical drive.\n\nBrowse to `http://your-host-ip:5800` to access the MakeMKV GUI.\nFiles from the host appear under the `/storage` folder in the container.\n\n## Usage\n\n```\ndocker run [-d] \\\n --name=makemkv \\\n [-e =]... \\\n [-v :[:PERMISSIONS]]... \\\n [-p :]... \\\n jlesage/makemkv\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|`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|`MAKEMKV_KEY`| MakeMKV registration key to use. The key is written to the configuration file during container startup. When set to `BETA`, the latest beta key is automatically used. When set to `UNSET`, no key is automatically written to the configuration file. | `BETA` |\n|`AUTO_DISC_RIPPER`| When set to `1`, the automatic disc ripper is enabled. | `0` |\n|`AUTO_DISC_RIPPER_EJECT`| When set to `1`, disc is ejected from the drive when ripping is terminated. | `0` |\n|`AUTO_DISC_RIPPER_PARALLEL_RIP`| When set to `1`, discs from all available optical drives are ripped in parallel. Else, each disc from optical drives is ripped one at time. | `0` |\n|`AUTO_DISC_RIPPER_INTERVAL`| Interval, in seconds, the automatic disc ripper checks for the presence of a DVD/Blu-ray discs. | `5` |\n|`AUTO_DISC_RIPPER_MIN_TITLE_LENGTH`| Titles with a length less than this value are ignored. Length is in seconds. By default, no value is set, meaning that value from MakeMKV's configuration file is taken. | (unset) |\n|`AUTO_DISC_RIPPER_BD_MODE`| Rip mode of Blu-ray discs. `mkv` is the default mode, where a set of MKV files are produced. When set to `backup`, a copy of the (decrypted) file system is created instead. **NOTE**: This applies to Blu-ray discs only. For DVD discs, MKV files are always produced. | `mkv` |\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`| ro | This location contains files from your host that need to be accessible by the application. |\n|`/output`| rw | This is where extracted videos are written. |\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| 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| 51000 | Optional | Port used by the streaming service. |\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 makemkv\n```\n 2. Remove the container:\n```\ndocker rm makemkv\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 Compose File\n\nHere is an example of a `docker-compose.yml` file that can be used with\n[Docker Compose](https://docs.docker.com/compose/overview/).\n\nMake sure to adjust according to your needs. Note that only mandatory network\nports are part of the example.\n\n```yaml\nversion: '3'\nservices:\n makemkv:\n build: .\n ports:\n - \"5800:5800\"\n volumes:\n - \"/docker/appdata/makemkv:/config:rw\"\n - \"$HOME:/storage:ro\"\n - \"$HOME/MakeMKV/output:/output:rw\"\n devices:\n - \"/dev/sr0:/dev/sr0\"\n - \"/dev/sg2:/dev/sg2\"\n```\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 jlesage/makemkv\n```\n 2. Stop the container:\n```\ndocker stop makemkv\n```\n 3. Remove the container:\n```\ndocker rm makemkv\n```\n 4. Start the container using the `docker run` command.\n\n### Synology\n\nFor owners of a Synology NAS, the following steps can be use to update a\ncontainer image.\n\n 1. Open the *Docker* application.\n 2. Click on *Registry* in the left pane.\n 3. In the search bar, type the name of the container (`jlesage/docker-makemkv`).\n 4. Select the image, click *Download* and then choose the `latest` tag.\n 5. Wait for the download to complete. A notification will appear once done.\n 6. Click on *Container* in the left pane.\n 7. Select your MakeMKV container.\n 8. Stop it by clicking *Action*->*Stop*.\n 9. Clear the container by clicking *Action*->*Clear*. This removes the\n container while keeping its configuration.\n 10. Start the container again by clicking *Action*->*Start*. **NOTE**: The\n container may temporarily disappear from the list while it is re-created.\n\n### unRAID\n\nFor unRAID, a container image can be updated by following these steps:\n\n 1. Select the *Docker* tab.\n 2. Click the *Check for Updates* button at the bottom of the page.\n 3. Click the *update ready* link of the container to be updated.\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 \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://:5800\n```\n\n * Any VNC client:\n```\n:5900\n```\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`makemkv.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 docker-makemkv {\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 makemkv.domain.tld;\n\n\tlocation / {\n\t proxy_pass http://docker-makemkv;\n\t}\n\n\tlocation /websockify {\n\t\tproxy_pass http://docker-makemkv;\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/makemkv` 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 docker-makemkv {\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 = /makemkv {return 301 $scheme://$http_host/makemkv/;}\n\tlocation /makemkv/ {\n\t\tproxy_pass http://docker-makemkv/;\n\t\tlocation /makemkv/websockify {\n\t\t\tproxy_pass http://docker-makemkv/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## Access to Optical Drive(s)\n\nBy default, a Docker container doesn't have access to host's devices. However,\naccess to one or more devices can be granted with the `--device DEV` parameter.\n\nIn the Linux world, an optical drive is represented by two different device\nfiles: `/dev/srX` and `/dev/sgY`, where `X` and `Y` are numbers.\n\nFor best performance, it is recommended to expose both these devices to the\ncontainer. For example, for an optical drive represented by `/dev/sr0` and\n`/dev/sg1`, the following parameters would be added to the `docker run`\ncommand:\n```\n--device /dev/sr0 --device /dev/sg1\n```\n\n**NOTE**: For an optical drive to be detected by MakeMKV, it is mandatory to\nexpose `/dev/sgY` to the container. `/dev/srX` is optional, but performance\ncould be affected.\n\nThe easiest way to determine the right Linux devices to expose is to run the\ncontainer (without `--device` parameter) and look at its log: during the\nstartup, messages similar to these ones are outputed:\n```\n[cont-init.d] 95-check-optical-drive.sh: executing...\n[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...\n[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg3], but it is not usable because:\n[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sr0 is not exposed to the container.\n[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg3 is not exposed to the container.\n[cont-init.d] 95-check-optical-drive.sh: no usable optical drive found.\n[cont-init.d] 95-check-optical-drive.sh: exited 0.\n```\n\nIn this case, it's clearly indicated that `/dev/sr0` and `/dev/sg3` needs to be\nexposed to the container.\n\n## Automatic Disc Ripper\n\nThis container has an automatic disc ripper built-in. When enabled, any DVD or\nBlu-ray video disc inserted into an optical drive is automatically ripped. In\nother words, MakeMKV decrypts and extracts all titles (such as the main movie,\nbonus features, etc) from the disc to MKV files.\n\nTo enable the automatic disc ripper, set the environment variable\n`AUTO_DISC_RIPPER` to `1`.\n\nTo eject the disc from the drive when ripping is terminated, set the environment\nvariable `AUTO_DISC_RIPPER_EJECT` to `1`.\n\nIf multiple drives are available, discs can be ripped simultaneously by\nsetting the environment variable `AUTO_DISC_RIPPER_PARALLEL_RIP` to `1`.\n\nSee the [Environment Variables](#environment-variables) section for details\nabout setting environment variables.\n\n**NOTE**: All titles, audio tracks, chapters, subtitles, etc are\n extracted/preserved.\n\n**NOTE**: Titles and audio tracks are kept in their original format. They are\n not transcoded or converted to other formats or into smaller sizes.\n\n**NOTE**: Ripped Blu-ray discs can take a large amount of disc space (~40GB).\n\n**NOTE**: MKV Files are written to the `/output` folder of the container.\n\n**NOTE**: The automatic disc ripper processes all available optical drives.\n\n## Troubleshooting\n\n### Expired Beta Key\n\nIf the beta key is expired, just restart the container to automatically fetch\nand install the latest one.\n\n**NOTE**: For this solution to work, the `MAKEMKV_KEY` environment variable must\nbe set to `BETA`. See the [Environment Variables](#environment-variables)\nsection for more details.\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\nFor other great Dockerized applications, see https://jlesage.github.io/docker-apps.\n\n[create a new issue]: https://github.com/jlesage/docker-makemkv/issues\n","has_starred","hub_user","immutable_tags_settings",{"_70":11,"_71":72},"enabled","rules",[73],".*","is_automated","permissions",{"_77":17,"_78":11,"_79":11},"read","write","admin","user","storage_size",122928596,"orgData","recentTags",[86,124],{"_87":39,"_88":89,"_90":91,"_92":93,"_94":95,"_45":113,"_114":89,"_115":28,"_116":51,"_52":117,"_118":119,"_120":104,"_121":113,"_122":61,"_123":17},"content_type","creator",2026788,"full_size",122890370,"id",33390896,"images",[96],{"_97":98,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":102,"_110":-5,"_111":91,"_58":61,"_112":-5},"architecture","amd64","digest","sha256:c3dd15dd978e560585fbf14ec8417a141a516a25e78ac72029a5db3866dcefd3","features","","last_pulled","2026-09-16T18:17:37.273342342Z","last_pushed","2018-08-18T22:38:12Z","os","linux","os_features","os_version","size","variant","2018-08-18T22:38:13.934101Z","last_updater","last_updater_username","media_type","latest","repository",5904751,"tag_last_pulled","tag_last_pushed","tag_status","v2",{"_87":39,"_88":89,"_90":91,"_92":125,"_94":126,"_45":128,"_114":89,"_115":28,"_116":51,"_52":129,"_118":119,"_120":104,"_121":128,"_122":61,"_123":17},33390895,[127],{"_97":98,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":102,"_110":-5,"_111":91,"_58":61,"_112":-5},"2018-08-18T22:38:11.285865Z","v1.9.1","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_33":139,"_146":147,"_135":160,"_161":11},{"_35":140,"_37":141,"_40":41,"_42":43,"_44":11,"_45":46,"_47":48,"_49":142,"_52":30,"_27":28,"_53":54,"_55":39,"_56":57,"_58":59,"_60":61,"_62":-5,"_63":57,"_64":65,"_66":11,"_67":28,"_68":143,"_74":17,"_75":145,"_80":28,"_81":82},[],[39],[51],{"_70":11,"_71":144},[73],{"_77":17,"_78":11,"_79":11},"tags",{"_148":149,"_150":-5,"_151":-5,"_152":153},"count",2,"next","previous","results",[154,157],{"_87":39,"_88":89,"_90":91,"_92":93,"_94":155,"_45":113,"_114":89,"_115":28,"_116":51,"_52":117,"_118":119,"_120":104,"_121":113,"_122":61,"_123":17},[156],{"_97":98,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":102,"_110":-5,"_111":91,"_58":61,"_112":-5},{"_87":39,"_88":89,"_90":91,"_92":125,"_94":158,"_45":128,"_114":89,"_115":28,"_116":51,"_52":129,"_118":119,"_120":104,"_121":128,"_122":61,"_123":17},[159],{"_97":98,"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":102,"_110":-5,"_111":91,"_58":61,"_112":-5},[],"canDeleteTags","actionData","errors"]

dismantl/docker-makemkv

Tags for dismantl/docker-makemkv