Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Didn't work with docker swarm #64

Closed
zorion79 opened this issue May 5, 2021 · 1 comment
Closed

Didn't work with docker swarm #64

zorion79 opened this issue May 5, 2021 · 1 comment

Comments

@zorion79
Copy link

zorion79 commented May 5, 2021

If my service run on one node and reproxy on another node then reproxy didn't find service container. If both run on one node then all working.
API for services exist. https://docs.docker.com/engine/api/v1.41/#operation/ServiceList
Can we add this function?

@umputun
Copy link
Owner

umputun commented May 5, 2021

well, it exists with some form of orchestration on top of the docker, in this case - the swarm. Docker itself can be accessed remotely but such configuration is unusual and even exotic to be supported here.

The closest thing to such a multi-node discovery will be the support of consul catalog #56 as soon as @negasus completes it.

I moved it to discussions because this is outside of the core functionality of the reproxy

@umputun umputun closed this as completed May 5, 2021
Repository owner locked and limited conversation to collaborators May 5, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants