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.

Sign up for GitHub

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

Jump to bottom

Ensure Che image publishing is multiarch #17124

Closed
nickboldt opened this issue Jun 9, 2020 · 4 comments
Closed

Ensure Che image publishing is multiarch #17124

nickboldt opened this issue Jun 9, 2020 · 4 comments
Labels
area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/ci CI build and releases, PR testing, & whitelabel/productization issues help wanted Community, we are fully engaged on other issues. Feel free to take this one. We'll help you! kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Jun 9, 2020 •
edited
Loading

Today the che-release repo controls che releases, and uses docker push to publish, which I believe is a single-arch solution.

Entrypoint:

Example of using docker push:

Instead, we should switch to using skopeo copy to allow mutliarch images in Quay.

Or maybe use buildx, as suggested in #16287
@nickboldt nickboldt added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jun 9, 2020
@nickboldt nickboldt mentioned this issue Jun 9, 2020
Merged
@nickboldt nickboldt added area/ci CI build and releases, PR testing, & whitelabel/productization issues help wanted Community, we are fully engaged on other issues. Feel free to take this one. We'll help you! labels Jun 9, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jun 9, 2020
@nickboldt nickboldt mentioned this issue Jun 9, 2020
Closed
6 tasks
@tolusha tolusha removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jun 10, 2020
@abhay1722 abhay1722 mentioned this issue Jun 12, 2020
Closed
@prabhav-thali prabhav-thali mentioned this issue Jun 12, 2020
Closed
@shahidhs-ibm shahidhs-ibm mentioned this issue Jul 22, 2020
Closed
This was referenced Jan 5, 2021
Merged
Merged
@che-bot
Copy link
Contributor

che-bot commented Jan 20, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2021
@nickboldt
Copy link
Contributor Author

registries, server, and theia are still not multiarch in quay.

@nickboldt nickboldt added area/productization and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 3, 2021
@nickboldt nickboldt added the area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 label Apr 28, 2021
@nickboldt
Copy link
Contributor Author

With the demise of Travis CI, this is once again stalled.

@nickboldt nickboldt added the severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. label Sep 28, 2021
@che-bot
Copy link
Contributor

che-bot commented Mar 27, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 27, 2022
@che-bot che-bot closed this as completed Apr 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci/multi-arch Issues and PRs related to the release of images targeting architectures other than amd64 area/ci CI build and releases, PR testing, & whitelabel/productization issues help wanted Community, we are fully engaged on other issues. Feel free to take this one. We'll help you! kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nickboldt @tolusha @mkuznyetsov @che-bot