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

Why is consul started before weave #663

Closed
sheerun opened this issue Mar 1, 2016 · 4 comments
Closed

Why is consul started before weave #663

sheerun opened this issue Mar 1, 2016 · 4 comments

Comments

@sheerun
Copy link
Contributor

sheerun commented Mar 1, 2016

Hey

Just wondering why you start consul before weave and then restart it instead just starting weave before consul? Any reason?
@sheerun
Copy link
Contributor Author

sheerun commented Mar 1, 2016

Also, why you use public ips for consul instead of weave network

@enxebre
Copy link
Contributor

enxebre commented Mar 1, 2016

Hey @sheerun correct, consul should be running after so it runs on the weave network so it can run health checks on weave net.

@enxebre
Copy link
Contributor

enxebre commented Mar 1, 2016

#665

@tayzlor
Copy link
Member

tayzlor commented Mar 1, 2016

Closing via #665

@tayzlor tayzlor closed this as completed Mar 1, 2016
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
3 participants
@sheerun @enxebre @tayzlor