[
https://issues.apache.org/jira/browse/YUNIKORN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092265#comment-18092265
]
Wilfred Spiegelenburg commented on YUNIKORN-3222:
-------------------------------------------------
This also affects the e2e tests and the pre-load of images in kind.
The issue is related to the manifest files in the multi architecture images.
Docker only pulls down the one architecture it needs locally but leaves the
manifest intact. This results in empty entries in the manifest which seems to
be the trigger for: [https://github.com/kubernetes-sigs/kind/issues/3795]
For now the recommendation is to not use containerd until we figure this all
out.
> Multi architecture build fails with containerd in docker
> --------------------------------------------------------
>
> Key: YUNIKORN-3222
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3222
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: release
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Critical
>
> When the python image build script is run as part of the release process in a
> setup where docker is configured with containerd instead of the old docker
> image store the build.
> The build fails to load the manifest with a message like:
> {{docker.io/my-repo/my-image-arm64:<some-tag> is a manifest list}}
> With containerd as the store we can directly build multi architecture images.
> Containerd is the default for new docker setups and we should leverage that
> to allow a local multi architecture image build.
> It would simplify the image build process and thus the release process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
