Yeah watchtower pushed it on my development box this morning and it took down everything due to the config changes heh. Went back to 1.7 and it came right back up though. I look forward to migrating to 2 but will give some time to let the migration guide documentation to finish.
Let’s see how many people broke their systems because they were using `latest` in production instead of `1.7` or another fixed tag.
I tried 2.0 yesterday on a test system and while it looks great I am struggling to configure things that were easy in 1.x:
* ~~Doesn’t recognize custom tls or header configurations from the file on docker labels.~~ Fixed, put those in separate files.
* A simple https redirect is extremely verbose as you have to redeclare the host. https://github.com/containous/traefik/issues/4863
* ~~I get parse errors when mixing config files with dynamic directory watcher (on yaml)~~ Fixed, probably my fault.
* ~~Other stuff that I cannot remember right now.~~ https://github.com/containous/traefik/issues/5134
I just need some free time to build some test cases and open some bugs, but some things like the redirect one seems like a huge oversight.
Woke up this morning and all my docker services were inaccessible. Not sure why they didn’t make it backwards compatible with the older versions, or at least not have migration documentation (or make sure the documentation servers didn’t go down on release day).
Sounds neat but i’m just going to unfuck my existing services with a :v1.7 tag and wait for someone smarter than me to write some more blog posts for me to read about 2.0 before I bother.
So, if I am planning to play with traefik and get it going on my test server, which version should I focus on?
Thinking to stick with 1.7 as there are more guides to google out for morons like me… but that yaml config support seems kinda interesting, that its unifying docker and traefik.
v2 is great 🙂 Thanks for all of your hard work!
Yeah watchtower pushed it on my development box this morning and it took down everything due to the config changes heh. Went back to 1.7 and it came right back up though. I look forward to migrating to 2 but will give some time to let the migration guide documentation to finish.
What’s with all the strikethrough’s in the blog post? I can’t tell what’s supported in 2.0 and what isn’t.
Edit: Oh, weird. On mobile, all the underlined links to GH issues are showing as strikethroughs for me.
Do you still need to expose the Docker socket to the web-facing container?
Let’s see how many people broke their systems because they were using `latest` in production instead of `1.7` or another fixed tag.
I tried 2.0 yesterday on a test system and while it looks great I am struggling to configure things that were easy in 1.x:
* ~~Doesn’t recognize custom tls or header configurations from the file on docker labels.~~ Fixed, put those in separate files.
* A simple https redirect is extremely verbose as you have to redeclare the host. https://github.com/containous/traefik/issues/4863
* ~~I get parse errors when mixing config files with dynamic directory watcher (on yaml)~~ Fixed, probably my fault.
* ~~Other stuff that I cannot remember right now.~~ https://github.com/containous/traefik/issues/5134
I just need some free time to build some test cases and open some bugs, but some things like the redirect one seems like a huge oversight.
Me, I did that.
Couldn’t work out why stuff stopped working, it’s cuz V2 has very different settings!
Woke up this morning and all my docker services were inaccessible. Not sure why they didn’t make it backwards compatible with the older versions, or at least not have migration documentation (or make sure the documentation servers didn’t go down on release day).
Sounds neat but i’m just going to unfuck my existing services with a :v1.7 tag and wait for someone smarter than me to write some more blog posts for me to read about 2.0 before I bother.
So, if I am planning to play with traefik and get it going on my test server, which version should I focus on?
Thinking to stick with 1.7 as there are more guides to google out for morons like me… but that yaml config support seems kinda interesting, that its unifying docker and traefik.