> On Nov 1, 2017, at Nov 1, 3:28 AM, Aleksandar Lazic <[email protected]> wrote: > > > There is now a shiny new docker image with the rc1. > > docker run --rm --entrypoint /usr/local/sbin/haproxy me2digital/haproxy18 -vv >
For the past couple of years, I’ve also been maintaining a base docker image for haproxy. It is interesting to see how other’s structure the build and configuration. I see that you include a base / default configuration file while I’ve left that completely up to the user to provide one. Given how many different ways people use haproxy, it didn’t seem that there was any one “basic” config that would work beyond a trivial example. I’m curious how useful the configuration you’ve packaged is. I use my image as a base which I then repackage use-case specific configuration files into for deployments and I assume anyone else using the image does the same thing, but I do not have any feedback about that. https://hub.docker.com/r/fingershock/haproxy-base/ <https://hub.docker.com/r/fingershock/haproxy-base/> -Bryan
