Include libs for popular databases?

[circleci-public]

Include libs for popular databases?

[louim]

I can understand the appeal of having slim images. My honest opinion as a end user is that I want something that works. Main thing I look for in builds is speed. I don't mind if that's a separate step or not as long as it's well documented and it's faster. It's likely something that I will do setup once per project. What I don't want is something adding 15 seconds (I choose a totally random number here) to the build time, only for the sake of having a smaller base image 😄.

[felicianotech]

Not at all. Your feedback is very helpful. I just only hope we can get some more to share their opinions. If we do start adding in some database libs, I hope to get this in this month so it makes the June snapshot image.

[felicianotech]

Here's the idea on being strict on what enters the image. Keep in mind, I'm not speaking specifically about libpq here, which I'm leaning on including. This is the general philosophy.

What I don't want is something adding 15 seconds (I choose a totally random number here) to the build time, only for the sake of having a smaller base image

Having a smaller base image isn't about it literally being small. A smaller, less layers image downloads faster and is also less maintenance for our team (depending on what's added). The scenario we are trying to prevent is adding a bunch of tools that saves 20% of our users 15 seconds by increasing the download time for the image by 10 seconds for 80% of users.

[louim]

@felicianotech that's totally reasonable. Apologies if my previous comment sounded aggressive, that was not the intention.