[
https://issues.apache.org/jira/browse/YUNIKORN-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit updated YUNIKORN-1240:
-----------------------------------
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):
{code:java}
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{code}
Doing something similar for all four images would allow us to maintain the
"latest" images as before.
was:
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.
> 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
> Priority: Major
>
> 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):
> {code:java}
> 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{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: [email protected]
For additional commands, e-mail: [email protected]
