You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since you're new to Docker, I'll suggest starting out with https://github.com/Shreyas220/loadbalancer/issues/9 first to get a bit familiar.
In that issue, you'll basically create a github workflow which will build a docker image and push it to dockerhub.
Hello @DelusionalOptimist, in order to containerized load balancer is required to expose docker socket to the container, so this way the load balancer will be able to connect to docker and perform all the actions required. I just want to heads you up about the risks doing this, there is blog explaing it in details https://blog.quarkslab.com/why-is-exposing-the-docker-socket-a-really-bad-idea.html. As alternative solution I want to propose to leverage the cross-compile feature of go, to distribute an standalone executable using github releases feature. WDYT?
Context?
The way you would use the load balancer right now:
docker-compose up
- This runs your services in docker containers managed by compose../docker-lb
) - This runs the load balancer as a process in your system (outside containers)What's wrong with this?
So what changes can be done?
Note
Comment below if you'd like to work on this issue to indicate your interest and let us know so that we can assign you! 😄
The text was updated successfully, but these errors were encountered: