Update container images

[noliveleger]

• nginx
• postgresql
• mongo
• redis

Use official releases and last LTS version if any.

[sikado]

Hi Guys,

Is there a reason why you are using "custom" images instead of official images ? (like https://hub.docker.com/_/nginx , https://hub.docker.com/_/mongo or https://hub.docker.com/_/redis)
And more other, why to you use Ubuntu-based containers instead of a lightweight distrib which would have a smaller footprint on the system ?

I don't know if it's the best place to ask that, I can switch to the forum if you think it's more relevant
Thanks !

[noliveleger]

@sikado,
We do want to use official images. We already use official images for Mongo and Redis though (but not the latest version)
Ubuntu vs Alpine is a good question and we may switch to Alpine versions in the future. But, as you may know, we are a small team and we cannot do this in short or mid term.
PRs from the community are welcome ;-)

Indeed, it would be better to continue on the forum for this type of discussion.

[jeverling]

Hi everybody, just a quick aside on Debian/Ubuntu vs. Alpine: wheels.

Alpine uses a different libc (musl), which means that wheels that ship pre-compiled C-extensions don't work. So the C-extensions have to be compiled, which adds a lot of relics and takes time.
So usually, with Python based projects, you are actually better off and have smaller images in the end using the e.g. python-slim images instead of the Alpine based images.

Some more background here: https://pythonspeed.com/articles/alpine-docker-python/

This article exaggerates the issue probably a bit, but it's true that wheels will usually not work for Alpine. It is possible to use a hack to make the wheels work with Alpine, but that's actually quite dangerous due to the different libc.

So using the "slim" Python image variants is IMO much preferable over Alpine.