Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement multi-arch image building for oci-registry #1546

Closed
2 tasks
Tracked by #1492
Jdubrick opened this issue May 13, 2024 · 0 comments · Fixed by devfile/registry-support#240
Closed
2 tasks
Tracked by #1492

Implement multi-arch image building for oci-registry #1546

Jdubrick opened this issue May 13, 2024 · 0 comments · Fixed by devfile/registry-support#240
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@Jdubrick
Copy link
Contributor

Jdubrick commented May 13, 2024

Which area is this issue related to?

/area registry

Issue Description

Currently devfile/registry-support/oci-registry is able to have its image built for amd64 and arm64 platforms but it requires the use of --platform linux/amd64 or --platform linux/arm64 to do so. We should implement a manifest creation that allows us to build a multi-arch image so that anyone who wishes to pull built Devfile images has the option between amd64 or arm64.

Example from Red Hat Developer:

# First, initialise the manifest
podman manifest create <image name>

# Build the image attaching them to the manifest
podman build --platform linux/amd64,linux/arm64  --manifest <image name>  .

# Finally publish the manifest
podman manifest push <image name>

The above is a simple example and more research may be required to have this work smoothly. It may also be possible to allow the multi-arch images to be built in a shell script similar to build.sh and pushed like push.sh.

Once the manifest is created and apart of the repository, any automation that is currently building images for this repository and pushing them should be doing so to the manifest to allow for multi-arch pulling.

Acceptance Criteria

  • Able to build and push oci-registry image as a multi-arch image.
  • Any automations building images and pushing to quay.io should be pushing to that manifest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
Status: Done ✅
Development

Successfully merging a pull request may close this issue.

1 participant