[YUNIKORN-1240] Document changes required for RM multi-arch release builds

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: release
• Labels: pull-request-available
• Target Version: 1.1.0
• Assignee: Wilfred Spiegelenburg
• Reporter: Craig Condit
• Created: 17/Jun/22 20:02
• Updated: 13/Sep/22 14:31
• Resolved: 09/Aug/22 01:39

Description

Now that YUNIKORN-1215 is complete, we need to document the new process for producing Docker images.

A couple things needed in addition to the documentation of the scripts themselves:

1. When building on linux, builds will fail if QEMU is not configured or installed properly. At least on Debian, this requires the `qemu-user-static` package.

2. After the release, we traditionally update the `{image}-latest` tags to point to the new build. Now that these are multi-arch builds, this is a little tricky. We need to copy the manifest, which is not as simple as a re-tag and push.

We could use this tool: https://github.com/regclient/regclient.

I verified that this works on a personal account (changing username of course):

regctl registry login
regctl image copy apache/yunikorn:scheduler-1.1.0-test apache/yunikorn:scheduler-latest
regctl image copy apache/yunikorn:scheduler-plugin-1.1.0-test apache/yunikorn:scheduler-plugin-latest
regctl image copy apache/yunikorn:admission-1.1.0-test apache/yunikorn:admission-latest
regctl image copy apache/yunikorn:web-1.1.0-test apache/yunikorn:web-latest

Doing something similar for all four images would allow us to maintain the "latest" images as before.

Issue Links

• is related to: YUNIKORN-1215 Enable multi-arch release builds
• is related to: YUNIKORN-1243 Build replacement web UI image for e2e tests
• links to: GitHub Pull Request #170