Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When I try to run docker images of marathon-lb, the PORTS environment var has no effect. #590

Open
saturnman opened this issue May 29, 2018 · 1 comment
Open

When I try to run docker images of marathon-lb, the PORTS environment var has no effect. #590

saturnman opened this issue May 29, 2018 · 1 comment

Comments

@saturnman
Copy link

When I try to run docker images of marathon-lb, the PORTS environment var has no effect. Service port mapped to port 10001 by default, I dont't know where the environment variable PORTS is consumed when using docker images to run marathon-lb service.
@jarmoni
Copy link

jarmoni commented May 15, 2019

I can confirm this behaviour. It seems that the value of PORTS (if present) is just printed to stdout during startup but does not override the default (9090).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@saturnman @jarmoni