You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2026/08/27 02:44:00 UTC

[jira] [Commented] (YUNIKORN-3222) Multi architecture build fails with containerd in docker

    [ https://issues.apache.org/jira/browse/YUNIKORN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108615#comment-18108615 ] 

Wilfred Spiegelenburg commented on YUNIKORN-3222:
-------------------------------------------------

Stopping progress for now need to revisit this when we have a kind fix also that allows containerd without workarounds.

> 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: Major
>
> 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: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org