Docker.labelInjector
A Community Application plugin for Unraid that adds a quick way to bulk-add, modify, or remove Docker labels on selected containers from the Docker tab, so…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (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.
45/100 Fair
- Maintained
- 48last commit 249 days ago
- Popular
- 2620 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 85no serious findings, CI
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 4 days ago
- GitHub stars
- 20
- Open issues
- 0
- Last commit
- 2026-03-17
- Activity
- stale
Checked today - source: GitHub (phyzical/docker.labelInjector)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Pick a project folder before you start Use an example project folder such as projects/portland-metro because it contains the .env, docker-compose.yml, and pelias.json files the build needs. Starting elsewhere can make Docker use the wrong settings or fail. source
- Set DATA_DIR to a folder you keep Edit .env so DATA_DIR points to a real folder where Pelias can store downloaded maps and built data. If this path is missing, full, or gets deleted, downloads, imports, or restarts can fail. source
- Run the build steps in the shown order Follow the steps in order: pull images, start Elasticsearch, download data, prepare it, import it, then start the stack. Skipping or reordering steps can leave the database index incomplete or broken. source
- Install via Community Applications Install the plugin from Community Applications, then open the Docker tab and click Add Labels to assign label key/value pairs to chosen containers; entries use name=value or name=label=value syntax, a value of REMOVE deletes a label, and templates are backed up before any change. source
- First run After installing, open the Docker tab, click Add Labels, select containers, and enter NAME=LABEL or NAME=LABEL=VALUE. source
- Defaults Use the plugin settings page to define default labels that are prefilled each time. source
Fetched 44 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Can I apply label changes to several containers at once?
Yes. It provides a quick way to bulk-add, modify, or remove Docker labels on selected containers from the Docker tab.
Do I need to edit container YAML or compose files by hand?
No. It is intended to organize container templates without editing YAML by hand.
Will the labels automatically create a dashboard view?
A community thread asks whether a Docker dashboard can automatically populate items from container labels, but it does not confirm an automatic dashboard for this plugin.
What update practice applies if I auto-update containers labeled with this plugin?
Pin a major version tag to reduce Watchtower breakage, and any auto updates can break something, so a staging environment and manual upgrades are advised.
Answers sourced from github.com, www.reddit.com, www.reddit.com
Community
Collected 48 days ago - public community threads