-
Notifications
You must be signed in to change notification settings - Fork 501
Docker push multi-platform images #1026
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
Conversation
Signed-off-by: Varun Gupta <[email protected]>
|
Do you mean there's no easy way to manage different platforms |
Yeah, I think arm user they just need a release image and may not need it for every commit, I agree with your proposal . BTW, Instead of using the existing release workflow, can we create a separate job for arm users? Just in case it affect the current release flow (some of the steps are not idempotent) |
Sure, I will create different release workflow which will just upload arm image. Restore the docker-push-image workflow as-is. |
Signed-off-by: Varun Gupta <[email protected]>
Signed-off-by: Varun Gupta <[email protected]>
|
@Jeffwan Added a new release build for arm64. I tested the code via docker push image but to test release action it need to be merged first. Once merged I will test it out for previous release tags. Second, docs build is failing due to git checkout error (not related to PR). Can you rerun it? |
|
@varungup90 I just see the message. Let me double check the doc error |
|
@varungup90 I restart the doc build and it's working fine. |
Signed-off-by: Varun Gupta <[email protected]>
Signed-off-by: Varun Gupta <[email protected]>

Pull Request Description
[Please provide a clear and concise description of your changes here]
Related Issues
Resolves: #[Insert issue number(s)]
Important: Before submitting, please complete the description above and review the checklist below.
Contribution Guidelines (Expand for Details)
We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:
Pull Request Title Format
Your PR title should start with one of these prefixes to indicate the nature of the change:
[Bug]: Corrections to existing functionality[CI]: Changes to build process or CI pipeline[Docs]: Updates or additions to documentation[API]: Modifications to aibrix's API or interface[CLI]: Changes or additions to the Command Line Interface[Misc]: For changes not covered above (use sparingly)Note: For changes spanning multiple categories, use multiple prefixes in order of importance.
Submission Checklist
By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.