← Directory

MediaInfo

MediaInfo is a lightweight container for inspecting the technical and tag metadata of video and audio files.

  • Tools & Utilities
MediaInfo is a lightweight container for inspecting the technical and tag metadata of video and audio files. The Docker image exposes MediaInfo's graphical interface through a modern web browser or a VNC (Virtual Network Computing) client, with no client-side installation or configuration required. The Alpine-based image is efficient for resource-conscious homelabs that need quick media file inspection.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 23 days ago
Popular
3135 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
35
Open issues
1
Last commit
2026-09-22
Latest release
v26.09.1
License
MIT
Activity
declining

Checked 9 days ago - source: GitHub (jlesage/docker-mediainfo)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • These docs install helpers, not the app The listed commands install only the support libraries (the small helper files a program needs), not the MediaInfo program itself. Run the matching support-library command first, then install MediaInfo separately so you have something to open. source
  • Pick the command for your Linux system Use only the dependency block for the Linux distribution you are using (the flavor of Linux, like Ubuntu or Fedora). Installing the wrong set can cause errors or leave MediaInfo without the files it expects. source
  • Docker containers need the same support If you run MediaInfo in Docker (an isolated app container), make sure the container image also installs these support libraries. Without them, the container may fail to start or be unable to analyze media files. source
  • Access the web UI Open the container's web interface in a browser or connect with a VNC (Virtual Network Computing) client to inspect media files; no client-side installation is required. source

Fetched 9 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What port should I expose for the MediaInfo Docker GUI?

The quick start Docker command maps 5800:5800.

Where should the container store its configuration so I can back it up?

Mount a host directory to /config, such as /docker/appdata/mediainfo, which stores the application's configuration.

Do I need to install MediaInfo on my client computer to use the GUI?

No, the graphical interface can be accessed through a modern web browser or via any VNC client.

Can I browse files and open a terminal from the web interface?

Yes, the web interface includes an integrated file manager and terminal for accessing the container's files and shell.

Answers sourced from github.com

Community

Collected 16 days ago - public community threads