Docker Provider vs. File Provider for Version-Stable Routing

Answer

For maximum predictability during a major Traefik Proxy version migration, the File Provider generally provides better isolation against provider-specific syntax breaking changes than the Docker Provider. Routing is decoupled from container metadata and can be validated as a file before rollout, whereas Docker Provider routing depends on how the new binary interprets container labels.

Confirmed facts

• Traefik separates static configuration, which enables entrypoints and providers, from dynamic configuration, which defines routers, services and middleware.
• Both Docker Provider and File Provider populate dynamic configuration.
• Docker Provider syntax is label keys on containers. File Provider syntax is YAML or TOML in a mounted file.
• The dynamic configuration schema is shared across providers, so schema changes affect both.

Likely explanation

Major version jumps have historically altered Docker Provider label namespaces, defaults and provider behavior, which can cause label misinterpretation after upgrade. File Provider expressions are version-controlled and can be statically checked against the target Traefik version, reducing surprise outages from label changes. This does not eliminate risk from dynamic schema changes, which apply to both providers.

Configuration persistence when switching providers

Docker Provider state lives with containers and is recreated on redeploy. File Provider state lives in files or volumes mounted to Traefik.

Switching providers during a recovery event requires translating routing intent between labels and file, creates two sources of truth and drift risk, and needs an atomic cutover with the provider enabled in static config. Mixing providers for the same routes can cause duplicate or conflicting routers and unpredictable precedence during upgrade and rollback.

Steps for this case

1. Pin the target Traefik major version and review its release notes for deprecated label keys and dynamic configuration schema changes.
2. Render the current routing intent into File Provider format and keep it in version control.
3. Validate the file with the candidate Traefik binary in a staging environment and compare generated dynamic configuration before and after upgrade.
4. Keep the previous Traefik image available for rollback and snapshot current dynamic configuration.
5. Enable both providers temporarily only with non-overlapping routers to avoid conflicts during migration, then cut over atomically.

Assumption and uncertainty: The degree of isolation depends on the specific major versions involved and whether you require automatic service discovery for frequently changing containers. File Provider does not immunize against breaking changes in Traefik's dynamic configuration schema.

One diagnostic detail that changes the recommendation: Which major versions are you moving between and is routing currently expressed exclusively via Docker labels or already mixed with File Provider? That determines the translation effort and rollback plan.