Align upstream alpine images

[tobybellwood]

Currently, there are different versions of the alpine upstream images in use across the various amazeeio images:

commons uses alpine (3.10 currently)

• https://github.com/amazeeio/lagoon/blob/master/images/commons/Dockerfile#L1

mariadb uses alpine:3.8

• https://github.com/amazeeio/lagoon/blob/master/images/mariadb/Dockerfile#L3

varnish uses alpine:3.7

• https://github.com/amazeeio/lagoon/blob/master/images/varnish/Dockerfile#L18

php uses phpXX-fpm-alpine (3.10 currently)

• https://github.com/amazeeio/lagoon/blob/master/images/php/fpm/Dockerfile#L5
• https://github.com/docker-library/php/blob/master/7.2/alpine3.10/fpm/Dockerfile#L7

nginx uses openresty/openresty:alpine (3.9 currently)

• https://github.com/amazeeio/lagoon/blob/master/images/nginx/Dockerfile#L3
• https://github.com/openresty/docker-openresty/blob/master/alpine/Dockerfile#L5

node uses node:XX-alpine (3.9 currently)

• https://github.com/amazeeio/lagoon/blob/master/images/node/Dockerfile#L4
• https://github.com/nodejs/docker-node/blob/master/10/alpine/Dockerfile#L1

python uses python:XX-alpine (3.10 currently)

• https://github.com/amazeeio/lagoon/blob/master/images/python/Dockerfile#L4
• https://github.com/docker-library/python/blob/master/3.7/alpine3.10/Dockerfile#L7

This could lead to potential confusion about what images may be susceptible to vulnerabilities and could benefit from being better aligned.

Where we can control and align the versions, we should - certainly updating the ones we've got set at early versions (unless there's a specific reason?)

[vincenzodnp]

I noticed it today writing documentation.
If not a specific reason why we should alig versions.

[tobybellwood]

In addition - alpine-based solr images are no longer being provided in the solr namespace on dockerhub (as per docker-solr/docker-solr#213)

https://github.com/wodby/base-solr could be an alternative - the decision whether to align base images or base off official (debian-based) images is more important.

[vincenzodnp]

In addition - alpine-based solr images are no longer being provided in the solr namespace on dockerhub (as per docker-solr/docker-solr#213)

We should use official Solr Slim images

[Schnitzel]

@vincenzodnp
Link to the Solr Slim Images? Reasoning why we should use them?

[tobybellwood]

I've looked into this a bit - as openjdk (which solr is built on) no longer provides official alpine images, we could either build it ourselves (😱) or use the official Debian (Buster) slim images (🤔)

Inheritance:
solr:7.7-slim (https://github.com/docker-solr/docker-solr/blob/master/7.7/slim/Dockerfile)
openjdk:11-jre-slim (https://github.com/docker-library/openjdk/blob/master/11/jre/slim/Dockerfile)
debian:buster-slim (https://github.com/debuerreotype/docker-debian-artifacts/blob/dist-amd64/buster/slim/Dockerfile)

[vincenzodnp]

@Schnitzel @tobybellwood Sorl 7.7.1 is the latest with alpine image (See the PR #1731)
Newer versions are built only on slim version as Toby said above

[tobybellwood]

closing, as mostly done, and the rest under control