Aleks, Am 17.05.19 um 10:34 schrieb Aleksandar Lazic: > I don't see a difference from concept point of view if there is a autobuild > from > docker hub or a open repository which pushes the image after the build.
There is: For the autobuild I can know *for sure* that the contents match the labeling. For the manual push I don't know whether it actually is the one CI pushed or whether CI just pretended to push, while you pushed a modified, malicious version. >> [timwolla@~]docker run -it --rm haproxy:alpine haproxy -vv |grep TLSv >> OpenSSL library supports : TLSv1.0 TLSv1.1 TLSv1.2 TLSv1.3 > > Well I agree with Илья. I personally don't like alpine, but that's my own > preference. I'm sure there are enough people which like it and use it. I generally prefer the Debian based images myself and I don't understand the "hype" for the absolute minimal size either. Because of Docker's layers the base image is only stored once and disk space is cheap. >> As a Docker user (and official image maintainer) and HAProxy user (and >> code contributor) I believe that the docker-official-images HAProxy >> image is the best general purpose (!) image you can find and I believe >> that the DOI team does a good job maintaining those images to be useful >> for the majority of users. > > To summarize the feedback for now. > > The docker-official-images HAProxy is a good. > > I will still build the images for me as I like to add some contrib features > like > prometheus and spoa-server. > I can fully agree with that :-) Best regards Tim Düsterhus
