Google Git
Sign in
apache / kafka / refs/heads/trunk / . / docker
tree: 4b0f21c67a7a81e95bf9fdbf8809d84caed6a962 [path history] [tgz]
  1. docker_official_images/
  2. examples/
  3. jvm/
  4. native/
  5. resources/
  6. test/
  7. common.py
  8. docker_build_test.py
  9. docker_official_image_build_test.py
  10. docker_release.py
  11. extract_docker_official_image_artifact.py
  12. generate_kafka_pr_template.py
  13. prepare_docker_official_image_source.py
  14. README.md
  15. requirements.txt
docker/README.md

Docker Images

Introduction

This directory contains scripts to build, test, push and promote docker image for kafka. All of the steps can be either performed locally or by using Github Actions.

Github Actions

  • Github Actions can be accessed in Actions tab of the repository.
  • Please ensure that whichever Github Action Workflow you are triggering, you are doing it for the correct branch.
  • For all Github Actions Workflows for docker images, you'll get the option to select the branch as a dropdown box.

Repository Setup

Make sure the DOCKERHUB_USER and DOCKERHUB_TOKEN secrets are added and made available to Github Actions in Github Repository settings. This is required for pushing the docker image.

Building image and running tests using github actions

  • This is the recommended way to build, test and get a CVE report for the docker image.

  • Just choose the image type and provide kafka url to Docker Build Test workflow. It will generate a test report and CVE report that can be shared with the community.

  • kafka-url - This is the url to download kafka tarball from. For example kafka tarball url from (https://archive.apache.org/dist/kafka). For building RC image this will be an RC tarball url.

  • image-type - This is the type of image that we intend to build. This will be dropdown menu type selection in the workflow. jvm image type is for official docker image (to be hosted on apache/kafka) as described in KIP-975

  • Example:- To build and test a jvm image type ensuring kafka to be containerised should be https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz (it is recommended to use scala 2.13 binary tarball), following inputs in github actions workflow are recommended.

image_type: jvm
kafka_url: https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz

Creating a Release Candidate using github actions

  • This is the recommended way to push an RC docker image.
  • Go to Build and Push Release Candidate Docker Image Github Actions Workflow.
  • Choose the image_type and provide kafka_url that needs to be containerised in the rc_docker_image that will be pushed to github.
  • Example:- If you want to push a jvm image which contains kafka from https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz to dockerhub under the namespace apache, repo name as kafka and image tag as 3.6.0-rc1 then following values need to be added in Github Actions Workflow:-
image_type: jvm
kafka_url: https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz
rc_docker_image: apache/kafka:3.6.0-rc0

Promoting a Release Candidate using github actions

  • This is the recommended way to promote an RC docker image.
  • Go to Promote Release Candidate Docker Image Github Actions Workflow.
  • Choose the RC docker image (rc_docker_image) that you want to promote and where it needs to be pushed to (promoted_docker_image), i.e. the final docker image release.
  • Example:- If you want to promote apache/kafka:3.6.0-rc0 RC docker image to apache/kafka:3.6.0 then following parameters can be provided to the workflow.
rc_docker_image: apache/kafka:3.6.0-rc0
promoted_docker_image: apache/kafka:3.6.0

Cron job for checking CVEs in supported docker images

  • Docker Image CVE Scanner Github Action Workflow (present in .github/workflows/docker_scan.yml) will run nightly CVE scans and generate reports for docker image tags mentioned in the supported_image_tag array.
  • This workflow is branch independent. Only the workflow in trunk, i.e. the default branch will be considered.
  • In case a Critical or High CVE is detected, the workflow will fail.
  • It will generate the scan reports that can be checked by the community.
  • For every new release, this should be updated with the latest supported docker images.
  • For example:-
For supporting apache/kafka:3.6.0, apache/kafka:latest and apache/kafka:3.7.0-rc0, supported_image_tag array should be
supported_image_tag: ['3.6.0', 'latest', '3.7.0-rc0']
  • When RC for a version gets changed or when a bug fix release happens, this should be updated as well.
  • For example:-
For supporting apache/kafka:3.6.1, apache/kafka:latest and apache/kafka:3.7.0-rc1, tag array should be
supported_image_tag: ['3.6.1', 'latest', '3.7.0-rc1']

Local Setup

Make sure you have python (>= 3.7.x) and java (>= 17) (java needed only for running tests) installed before running the tests and scripts.

Run pip install -r requirements.txt to get all the requirements for running the scripts.

Make sure you have docker installed with support for buildx enabled. (For pushing multi-architecture image to docker registry)

Building image and running tests locally

  • docker_build_test.py script builds and tests the docker image.
  • kafka binary tarball url along with image name, tag and type is needed to build the image. For detailed usage description check python docker_build_test.py --help.
  • Sanity tests for the docker image are present in test/docker_sanity_test.py.
  • By default image will be built and tested, but if you only want to build the image, pass --build (or -b) flag and if you only want to test the given image pass --test (or -t) flag.
  • An html test report will be generated after the tests are executed containing the results.
  • Example :- To build and test an image named test under kafka namespace with 3.6.0 tag and jvm image type ensuring kafka to be containerised should be https://downloads.apache.org/kafka/3.6.0/kafka_2.13-3.6.0.tgz (it is recommended to use scala 2.13 binary tarball), following command can be used
python docker_build_test.py kafka/test --image-tag=3.6.0 --image-type=jvm --kafka-url=https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz

Creating a Release Candidate

  • docker_release.py script builds a multi-architecture image and pushes it to provided docker registry.
  • Ensure you are logged in to the docker registry before triggering the script.
  • kafka binary tarball url along with image name (in the format <registry>/<namespace>/<image_name>:<image_tag>) and type is needed to build the image. For detailed usage description check python docker_release.py --help.
  • Example:- To push an image named test under kafka dockerhub namespace with 3.6.0 tag and jvm image type ensuring kafka to be containerised should be https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz (it is recommended to use scala 2.13 binary tarball), following command can be used. (Make sure you have push access to the docker repo)
# kafka/test is an example repo. Please replace with the docker hub repo you have push access to.

python docker_release.py kafka/test:3.6.0 --kafka-url https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz
  • Please note that we use docker buildx for preparing the multi-architecture image and pushing it to docker registry. It's possible to encounter build failures because of buildx. Please retry the command in case some buildx related error occurs.

Promoting a Release Candidate

  • It's not recommended to promote the docker image locally, as we have github actions doing it in a convenient way, but if needed following command can be used to promote a Release Candidate image.
  • Example:- If you want to promote RC image apache/kafka:3.6.0-rc0 to apache/kafka:3.6.0, following command can be used
# Ensure docker buildx is enabled in your system and you have access to apache/kafka
docker buildx imagetools create --tag apache/kafka:3.6.0 apache/kafka:3.6.0-rc0

Using the image in a docker container

Please check this for usage guide of the docker image.