After a few hours I finally got traefik 2 to run with the new label formats and get access to the API dashboard. I'm pretty happy with the results albeit the things that aren't really well described in the documentation regarding ports and why with docker swarm you still have to expose some port even if you use the api@internal otherwise traefik isn't happy with a container not exposing any ports.
Then I realized that the acme.json config file wasn't directed to my /etc/traefik/acme.json but decided to create its own /acme.json everytime I restarted traefik. As a result each consecutive reboot forced traefik to ask again and again for certificates as each time the acme.json was removed...
Then I reached the limit rates and was wondering.. Is there a way to limit how often dns are queried? I've seen a couple of config file but no where I can find any information of what they're supposed to actually do:
I guess it's a delay but a delay of what and before a check of what? Is it a delay between checks or after a container is started?
Then my question is as I got working certificates between a few reboots when is it going to be back working? Can I keep traefik running and it will solve itself in a few days or should I disable https for some time. I fear the errors are making traefik do more request than necessary and locking itself perpetually.
The other thing is now that acme.json will not get removed/cleared is there a way to prevent / limit traefik to get the server locked like it is right now. It's not a big deal for me as it's my personal server but I'd like to upgrade our traefik 1.7 to 2.0 at work but I'm a bit scared to have it blow letsencrypt. That would be a bit more dramatic as it may impact quite a lot of important things.