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.

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

How to support the dynamic ip and port for web container by bamboo #207

Open
jaminlai opened this issue Jun 3, 2016 · 2 comments
Open

Comments

@jaminlai
Copy link

jaminlai commented Jun 3, 2016

hi, we deploy web container by marathon with bridge network, so that the container ip and service port would be changed when re-deployed or restart.

However, in practice it seems couldn't to get the container ip and service port by bamboo, so that it cann't write the info to haproxy.cfg which i expected.

It seems bamboo write the haproxy.cfg with the host ip and host bridge port but not the container ip and port such as 8080 in tomcat

Is it bamboo couldn't get the service port or container port such as 8080?

Thanks

@wangcaichao
Copy link

if you want get container port or ip ,you shoud use the env or api to try,but they provide service just use host ip and port.

@j1n6
Copy link
Contributor

j1n6 commented Jul 19, 2016

@jaminlai It seems like you need to modify the template so that the container networking feature can be utilized (instead of the host ip)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants