Skip to content
Discussion options

You must be logged in to vote

The stack trace points at Traefik dynamic config, not at Docker itself.

http is ending up as null (or missing inner keys) in a YAML file Traefik Manager reads. That happens easily if lines were deleted instead of commented and the file still parses but leaves http: empty/null. Then setup crashes on cfg.setdefault('http', {}).

What to try:

  1. Find every dynamic YAML file Traefik Manager mounts (including anything you edited before the reinstall). Each needs a valid top-level http: block, at minimum empty maps, for example:
http:
  routers: {}
  middlewares: {}
  services: {}
  1. Remove or fix broken files until http is never null.
  2. Wipe the Traefik Manager data directory on the host (not just t…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@YttraZZ
Comment options

@chr0nzz
Comment options

@YttraZZ
Comment options

Answer selected by YttraZZ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants