-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix marathon provider #1090
Fix marathon provider #1090
Conversation
3f8bbd5
to
8d6b91a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix. LGTM. 👍
CI is failing for Docker 1.13, might just be a flake. @diegooliveira, do you want to try to retrigger Travis ( |
@timoreimann CI is always failing with Docker 1.13... |
@emilevauge gotcha, thanks for the info. |
8d6b91a
to
ca43e5c
Compare
Needs another rebase. :-) |
af9e32c
to
247dcb4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks @diegooliveira
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐸
The IP-Per-Task PR introduced a bug using the marathon application port mapping. This port should be used only in the proxy server, the downstream connection should be always made with the task port. This commit fix the regression and adds a unit test to prevent new problems in this setup.
247dcb4
to
cbbb5f4
Compare
The IP-Per-Task PR introduced a bug using the marathon application
port mapping. This port should be used only in the proxy server, the
downstream connection should always be made with the task port.
This commit fix the regression and adds an unit test to prevent new
problems in this setup.
Fixes #1072