Versions Compared

Old Version 1

changes.mady.by.user Tina Tsou

Saved on

compared with

New Version 2

changes.mady.by.user Cristina Pauna

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The docker images are in the official repo now [1] and the docker build jobs passing [2].

[1] https://hub.docker.com/r/akraino/validation/

...

How to Connect Jenkins to DockerHub

@Eric Ball

Please describe the process, from docker file to imageThe Jenkins slaves are connected to Dockerhub through the LF scripts and no extra steps are needed from users.

How to setup Jenkins

Content WIPDocker needs to be installed on the Jenkins slave building the containers.


Docker file and image naming specifics to support Multi-Arch (Instruction Set Architecture)

Images that support multi-arch are handled with manifest list (a.k.a. fat manifest) mechanism.

When building an image for a specific arch, the arch is added in the tag of the image (e.g. akraino/validation:k8s-amd64-latest and akraino/validation:k8s-arm64-latest).

After the images are pushed in the dockerhub repo, the manifest can be created from the two images. Its name will be the same as the two images but with the arch removed from the tag (e.g. akraino/validation:k8s-latest).

When pulling the image, the name of the manifest is used (e.g. akraino/validation:k8s-latest); the correct image will be pulled based on the architecture of the host from which the pull is made.

To check the commands used to build, push and create the manifest in the Akraino validation project, check the build.mk and README filesContent WIP.