Is Docker Label Handling a nginx-proxy-manager Feature?

[Sascha-Block]

Labels are a mechanism for applying metadata to Docker objects, including:

• Images
• Containers
• Local daemons
• Volumes
• Networks
• Swarm nodes
• Swarm services

You can use labels to organize your images, record licensing information, annotate relationships between containers, volumes, and networks, or in any way that makes sense for your business or application.

Does nginx-proxy-manager provide Docker Label Handling as a Feature?

[chaptergy]

Short answer: no.

In what ways could it use those labels? Grouping the hosts? Suggesting new hosts? Is it even possible to get access to this label or labels of other containers from inside a docker container?

[Sascha-Block]

The labels can be used to define the routing. This is done directly in the yaml file and is quite intuitive.

A use case would be service injection.

Example:

If a patch is applied on a server and there is a downtime in connection with this, a page with service information can be comfortably displayed in the front end.

Other tools eg. Traefik allows to simply forward requests to a defined error page container.

Loadbalacing is also made very simple. Everything is done with 1-3 lines and the tracing feature is great. So you can see "which way" the requests take in your own infrastructure and make adjustments if necessary.

Such an easy handling would be a wish within the nginx-proxy-manager project...

[chaptergy]

I'm not sure I would know enough about the topic to be able to implement it. This most likely would have to be contributed by someone from the community. But automatic routing is always nice.
Somewhat related, someone created a separate utility in #506 (comment), which automatically creates hosts based on environment variables on the containers.