[build] Use CentOS/UBI 8.2 as Docker base image

[tylersmalley]

• Move to CentOS 8 and UBI 8 base images
• Cleanup Dockerfile by using template over string interpolation
• Adds retry logic to yum commands
• Adds org.opencontainers.* labels

Builds:

• kibana-8.0.0-SNAPSHOT-docker.tar.gz
• kibana-oss-8.0.0-SNAPSHOT-docker.tar.gz
• kibana-ubi8-8.0.0-SNAPSHOT-docker.tar.gz

Testing:

• Download one of the Docker images (kibana-8.0.0-SNAPSHOT-docker.tar.gz as an example)

• Load the image:

  $ docker load -i kibana-8.0.0-SNAPSHOT-docker.tar.gz
  Loaded image: docker.elastic.co/kibana/kibana:8.0.0-SNAPSHOT
  

• Run Kibana. Be sure to update the image name which was provided by the previous command. You will also need to have Elasticsearch running (example: yarn es snapshot from Kibana source root directory)

  docker run --rm --network host -e ELASTICSEARCH_HOSTS=http://127.0.0.1:9200 -e ELASTICSEARCH_USERNAME=elastic -e ELASTICSEARCH_PASSWORD=changeme docker.elastic.co/kibana/kibana:8.0.0-SNAPSHOT

Release note

Docker containers now use CentOS 8.2 as the base image, upgrading from 7.7.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[mieciu]

I'm going to keep an eye on it as it's going to affect Cloud 😉

[tylersmalley]

Here is the Elasticsearch UBI PR for comparison: elastic/elasticsearch#60742

[tylersmalley]

@elasticmachine merge upstream

[tylersmalley]

@jbudz want to give this another pass?

[tylersmalley]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: d0183c0

Build metrics

✅ unchanged

History

• 💚 Build #68143 succeeded 2a0fba0
• 💚 Build #67986 succeeded 32baec2
• 💚 Build #67645 succeeded 0d587ba
• 💚 Build #67628 succeeded 6afee207c23158c924b7ab62c44c52ca3004004d
• 💚 Build #67249 succeeded f68e47b1a582a0771249f2a80b44e9750b882286

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[jbudz]

Tested the images - the only note I have is do you think we should address

"Chromium sandbox provides an additional layer of protection, but is not supported for Linux Red Hat Linux 8.2 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'."}

[tylersmalley]

@jbudz, I believe that is OK since the container is running in a namespace already. @elastic/kibana-reporting-services can you confirm?

[jbudz]

approving pending any concerns from the reporting team - I've reviewed the code and tested the images otherwise.

[liza-mae]

LGTM, I built it off this PR and ran the Kibana UBI image against Elasticsearch latest snapshot.

[tylersmalley]

Pinged reporting team and this notice is expected and isn't an issue since Docker is already namespaced negating sandboxing.