[Feature Request]: Support for Service@swarm provider for Traefik v3+ & overrides for default overrides (middleware-manager discussion #46)

:speech_balloon: GitHub discussion middleware-manager #46 in Feature Request, started by Fredzer on GitHub

Hey, I setup MM within a Docker Swarm environment and made smooth progress to a stable setup but I noticed that all my services were being duplicated and that wasn’t clearing up after initial setup. During MM setup I also updated Traefik to 3.2.1 to try and resolve resource-override.yml issues where it autogenerated middleware features that my v2.11 did not support preventing Traefik from loading any more dynamic files…

Traefik v3 @​docker provider no longer directly supports swarm settings and @​swarm has been introduced for that specifically.

The resource-overrides.yml takes a copy of every service and stores it as @​docker which Traefik now detects as a new dynamic @​file service and loads it only to report service down error.
Also every service seems to default to a “letsencrypt” certificateResolver is not configured anywhere. The only one I have configured is called “main” and used by almost every service so I guess this is just a default? Possibly due to incomplete detection via @ provider disassociation? I’ve battled with MM over the resource-overrides.yml with correct info but it really puts up a fight and just blats in the overrides (fair enough I guess) a human override would be handy.

If any if this is human error then my bad but I’ve looked around and as usual there is zero mention of swarm and the src only takes @​docker into account.

I located the logic under the default-generator …


:speech_balloon: Join in here or on GitHub.