-
Notifications
You must be signed in to change notification settings - Fork 166
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
Update to HAProxy 2? #28
Comments
I'd love that, although TBH this project needs some more love than just updating to a newer HAProxy. I would probably switch it to using Traefik 2 instead, which is what I'm using these days and is much easier to configure. What would the community think about that? I also need to add tests. And the biggest problem is that this works perfectly as it is, so it's hard to justify deep changes 😅 |
Personally, I prefer the embedded HAProxy, It's much easier to connect to another container inside a compose file, such as netdata, rather than needing Traefik 2, etc configured. |
@yajo Which is lighter weight? I use traefik v2, I have 2 instances already, one public, one internal-only. Is it possible to proxy the socket without using an embedded traefik/haproxy and instead rely on an external container? For the time being, please could you update to the latest HAProxy and build a new image? |
Yes, the idea'd be the same, just using a different proxy that I'm more used to.
No idea, but it shouldn't be a big difference in any case.
To proxy the socket you need... a proxy! 🎉 😄 It can be in a container or not, that's up to you.
I'll try, although I admit that it is low priority here. A PR would help. I labeled this as Hacktoberfest, maybe somebody wants a T-Shirt and accelerates this 😊 |
HAProxy seems a little lighter on the use of memory. In my system the current version of docker-socket-proxy is using 19MB of RAM meanwhile Traefik2, with a simple configuration, is using 42MB. |
HAProxy 1.9 looks to be about 1.5 years old. Meanwhile HAProxy 2.2 is noted as being an LTS release, which might be a good base for this container.
I locally updated the image to use haproxy:2.2-alpine and the configuration file didn't produce any errors when tested using this version. Any thoughts about updating to a more recent HAProxy?
The text was updated successfully, but these errors were encountered: