8000 Multi-Arch - Patching Workflow Changes · Issue #991 · project-copacetic/copacetic · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Multi-Arch - Patching Workflow Changes #991

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

Open
robert-cronin opened this issue Mar 27, 2025 · 0 comments
Open

Multi-Arch - Patching Workflow Changes #991

robert-cronin opened this issue Mar 27, 2025 · 0 comments
9632
Labels
enhancement New feature or request

Comments

@robert-cronin
Copy link
Contributor

Single-Arch Patching

  • After each sub-manifest’s UpdateManifest is obtained, call the existing single-arch patch routine (e.g. Path function found at https://github.com/project-copacetic/copacetic/blob/main/pkg/patch/patch.go#L45) for each sub-arch.
  • If we have to handle QEMU (for cross-arch on a single node), ensure that logic is triggered per sub-manifest within the patchWithContext function.
    • Add instructions for manual set up of QEMU
    • Add a check for emulation (possibly by checking if vmx or svm are present in /proc/cpuinfo, or by just trying a simple command with binfmt and seeing if it fails or not)
    • If emulation is not enabled, then we can fall back to just patching the host arch image.
  • Add a --push flag for defining whether copa will push the image(s) when done (this is something that can be added for single-arch too). Existing issue can be found here: feat: add push flag to support pushing to registry directly #294

Final Multi-Arch Manifest Assembly

  • Add code to create a new multi-arch manifest referencing each newly patched sub-image.
  • Possibly push them to a registry with the user’s --push or --tag-suffix arguments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant
0