From 1b2d99922cd5cb2c34dcde5b8d8c2abca46b2609 Mon Sep 17 00:00:00 2001 From: Maximilian Dorninger <97409287+maxdorninger@users.noreply.github.com> Date: Mon, 5 Jan 2026 17:14:32 +0100 Subject: [PATCH] Switch to quay and add docker image documentation (#356) This PR changes all mentions of GHCR to Quay, adds docs about the registries MM is available on, adds docs about the available docker image tags, and adds the GHCR permission issue to the troubleshooting page. --- README.md | 3 +- Writerside/topics/configuration-overview.md | 33 ++++++++++++++++++++- Writerside/topics/troubleshooting.md | 13 +++++++- docker-compose.yaml | 2 +- 4 files changed, 46 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 308e59a..8d05a92 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ -MediaManager is modern software to manage your TV and movie library. It is designed to be a replacement for Sonarr, +MediaManager is a modern software to manage your TV and movie library. It is designed to be a replacement for Sonarr, Radarr, Overseer, and Jellyseer. It supports TVDB and TMDB for metadata, supports OIDC and OAuth 2.0 for authentication and supports Prowlarr and Jackett. @@ -63,7 +63,6 @@ docker compose up -d PuppiestDoggo   Seferino   - ## Star History [![Star History Chart](https://api.star-history.com/svg?repos=maxdorninger/MediaManager&type=Date)](https://www.star-history.com/#maxdorninger/MediaManager&Date) diff --git a/Writerside/topics/configuration-overview.md b/Writerside/topics/configuration-overview.md index 9a4b8a3..b425281 100644 --- a/Writerside/topics/configuration-overview.md +++ b/Writerside/topics/configuration-overview.md @@ -30,4 +30,35 @@ The recommended way to install and run Media Manager is using Docker and Docker * For more information on the available configuration options, see the [Configuration section](Configuration.md) of the documentation. - \ No newline at end of file + + +## MediaManager and MetadataRelay Docker Images + +MediaManager is available as a Docker image on both Red Hat Quay.io and GitHub Container Registry (GHCR): + +- `quay.io/maxdorninger/mediamanager` +- `ghcr.io/maxdorninger/mediamanager/mediamanager` + +MetadataRelay Images are also available on both registries: + +- `quay.io/maxdorninger/metadata_relay` +- `ghcr.io/maxdorninger/mediamanager/metadata_relay` + +From v1.12.1 onwards, both MediaManager and MetadataRelay images are available on both Quay.io and GHCR. +The reason for the switch to Quay.io as the primary image registry is due +to [GHCR's continued slow performance](https://github.com/orgs/community/discussions/173607). + + + You can use either the Quay.io or GHCR images interchangeably, + as they are built from the same source and the tags are the same across both registries. + + +### Tags + +Both registries support the following tags: +- `latest`: Points to the latest stable release. +- `master`: Points to the latest commit on the master branch (may be unstable). +- `X.Y.Z`: Specific version tags (e.g., `1.12.0`). +- `X.Y`: Points to the latest release in the X.Y series (e.g., `1.12`). +- `X`: Points to the latest release in the X series (e.g., `1`). +- `pr-`: Points to the latest commit in the specified pull request (e.g., `pr-67`). diff --git a/Writerside/topics/troubleshooting.md b/Writerside/topics/troubleshooting.md index a529a20..5e8a650 100644 --- a/Writerside/topics/troubleshooting.md +++ b/Writerside/topics/troubleshooting.md @@ -43,4 +43,15 @@ your media library, hard linking will not work. - If you configured a category with a special save path, carefully read this page about MM with qBittorrent save paths. -If it still doesn't work, please open an Issue. It is possible that a bug is causing the issue. \ No newline at end of file +If it still doesn't work, please open an Issue. It is possible that a bug is causing the issue. + +## Docker Image Pull Issues + +- If you get a 401 or 403 error when pulling the image from GHCR, this is not a permission issue with the + repository/image. It errors because your Docker client is misconfigured. +- This is not a MediaManager issue per se, so please don't open an issue about this on the MediaManager GitHub repo. + +### Possible Fixes: + +- [Unable to pull image from GitHub Container Registry (Stack Overflow)](https://stackoverflow.com/questions/74656167/unable-to-pull-image-from-github-container-registry-ghcr) +- [Try pulling the image from Quay.io](configuration-overview.md#mediamanager-and-metadatarelay-docker-images) diff --git a/docker-compose.yaml b/docker-compose.yaml index d5b0beb..f76e7a3 100644 --- a/docker-compose.yaml +++ b/docker-compose.yaml @@ -1,7 +1,7 @@ services: mediamanager: container_name: mediamanager_server - image: ghcr.io/maxdorninger/mediamanager/mediamanager:latest + image: quay.io/maxdorninger/mediamanager:latest ports: - "8000:8000" environment: