You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/06/17 20:03:00 UTC
[jira] [Created] (YUNIKORN-1240) Document changes required for RM multi-arch release builds
Craig Condit created YUNIKORN-1240:
--------------------------------------
Summary: Document changes required for RM multi-arch release builds
Key: YUNIKORN-1240
URL: https://issues.apache.org/jira/browse/YUNIKORN-1240
Project: Apache YuniKorn
Issue Type: Task
Components: release
Reporter: Craig Condit
Assignee: Wilfred Spiegelenburg
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:
# 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.
# 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:
{code:java}
regctl image copy username/yunikorn:scheduler-1.1.0 username/yunikorn:scheduler-latest {code}
Doing something similar for all four images would allow us to maintain the "latest" images as before.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org