Building Container Images

Two make targets exists to build container images automatically based on the locally checked out branch:

Developer images

Run make dev-docker-image to build a cilium-agent Docker image that contains your local changes.

DOCKER_DEV_ACCOUNT=quay.io/myaccount DOCKER_IMAGE_TAG=jane-developer-my-fix make dev-docker-image

Run make docker-operator-generic-image (respectively, docker-operator-aws-image or docker-operator-azure-image) to build the cilium-operator Docker image:

DOCKER_DEV_ACCOUNT=quay.io/myaccount DOCKER_IMAGE_TAG=jane-developer-my-fix make docker-operator-generic-image

The commands above assumes that your username for quay.io is myaccount. You can then push the image tag to your own registry for development builds:

docker push quay.io/myaccount/cilium-dev:jane-developer-my-fix-amd64

Official release images

Anyone can build official release images using the make target below.

DOCKER_IMAGE_TAG=v1.4.0 make docker-images-all

Official Cilium repositories

The following table contains the main container image repositories managed by Cilium team. It is planned to convert the build process for all images based on GH actions.

Image dependency:

[docker|quay].io/cilium/cilium
 depends on:
  quay.io/cilium/cilium-builder
   depends on:
    quay.io/cilium/cilium-runtime
     depends on:
      docker.io/cilium/cilium-iproute2
      docker.io/cilium/cilium-bpftool
      docker.io/cilium/cilium-llvm
  quay.io/cilium/cilium-envoy
   depends on:
    quay.io/cilium/cilium-envoy-builder
     depends on:
      quay.io/cilium/cilium-builder
       depends on:
        quay.io/cilium/cilium-runtime
         depends on:
          docker.io/cilium/cilium-iproute2
          docker.io/cilium/cilium-bpftool
          docker.io/cilium/cilium-llvm

Update cilium-builder and cilium-runtime images

Login to quay.io with your credentials to the repository that you want to update:

cilium-builder - contains Cilium build-time dependencies cilium-runtime - contains Cilium run-time dependencies

1. After login, select the tab “builds” on the left menu.

1. Click on the wheel.
2. Enable the trigger for that build trigger.

1. Confirm that you want to enable the trigger.

1. After enabling the trigger, click again on the wheel.
2. And click on “Run Trigger Now”.

1. A new pop-up will appear to select your desired branch.
2. If you’re interested in simply bumping the image to have the latest packages, then select the release branch (i.e. v1.7, v1.8). If you already have a branch that contains changes, select the branch that contains the new changes.

1. After selecting your branch click on “Start Build”.

1. Once the build has started you can disable the Build trigger by clicking on the wheel.
2. And click on “Disable Trigger”.

1. Confirm that you want to disable the build trigger.

1. Once the build is finished click under Tags (on the left menu).
2. Click on the wheel and;
3. Add a new tag to the image that was built.

1. Write the name of the tag that you want to give for the newly built image.
2. Confirm the name is correct and click on “Create Tag”.

1. After the new tag was created you can delete the other tag, which is the name of your branch. Select the tag name.
2. Click in Actions.
3. Click in “Delete Tags”.

1. Confirm that you want to delete tag with your branch name.

You have created a new image build with a new tag. The next steps should be to update the repository root’s Dockerfile so that it points to the new cilium-builder or cilium-runtime image recently created.

1. Update the versions of the images that are pulled into the CI VMs.

• Open a PR against the Packer-CI-Build with an update to said image versions. Once your PR is merged, a new version of the VM will be ready for consumption in the CI.
• Update the SERVER_VERSION field in test/Vagrantfile to contain the new version, which is the build number from the Jenkins Job for the VMs. For example, build 119 from the pipeline would be the value to set for SERVER_VERSION.
• Open a pull request with this version change in the cilium repository.

Nightly Docker image

After each successful Nightly build, a cilium/nightly image is pushed to dockerhub.

To use latest nightly build, please use cilium/nightly:latest tag. Nightly images are stored on dockerhub tagged with following format: YYYYMMDD-<job number>. Job number is added to tag for the unlikely event of two consecutive nightly builds being built on the same date.