-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Support multiple docker sockets/proxy #162
Comments
Interesting! Seems easy to do! Not the ability to connect to multiple docker deamons at once, is that correct ? |
@acouvreur yes correct! So maybe in the sablier.yml we can define all the endpoints (default can be |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This would be great to have. I put as many containers as possible to the TCP endpoint of https://github.com/Tecnativa/docker-socket-proxy and only expose the portions of the socket that are needed instead of direct socket access. |
I agree on this. I prefer to use a docker proxy, instead of socket access.
|
Figured it out,... the docker client used picks up DOCKER_HOST and some other bits from the environment. See #287 |
Hi,
Love
sablier
!I believe this is not super unusual to have multiple docker connections. For example - For example, I've three currently:
So basically in the subrequest to sablier backend from nginx (or traefik), when using docker provider, it should also pass something like
sablierServer
which can then be used to start/stop/query container status.Homepage project (link) uses this concept to display the status and container stats.
The text was updated successfully, but these errors were encountered: