TraefikDocker

Configuration changes not applied due to missed redeployment or socket permissions

warning
configurationUpdated Jan 7, 2026(via Exa)
How to detect:

Labels edited in docker-compose.yml or service configuration but Traefik behavior unchanged. Common causes: service not redeployed after label changes, Traefik not receiving Docker events due to socket permission issues, or targeting wrong Traefik instance in multi-instance setup. Changes appear in compose file but not in running container labels.

Recommended action:

Redeploy affected container with 'docker compose up -d <service>'. Check Docker events are flowing with 'docker events --since 5m --filter type=container'. Verify Traefik can read Docker socket with 'docker exec -it traefik sh -lc "ls -l /var/run/docker.sock"'. Check Traefik logs for provider refresh messages. Confirm you're checking the correct Traefik instance. Validate rendered config with 'docker compose config' to ensure labels parsed correctly.