-
Notifications
You must be signed in to change notification settings - Fork 53
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
Multiarch support in upstream #559
Comments
Well, the images in RHEC for the 0.8.0 release are multi-arch X, Z, and P. https://catalog.redhat.com/software/containers/devworkspace/devworkspace-project-clone-rhel8/60ec9f47744684587e2186a1?architecture=ppc64le&container-tabs=overview>i-tabs=registry-tokens But we may have to build an upstream equivalent in GH actions / travis to achieve this in Che, unless Che also depends on the RHEC released product images. |
@nickboldt Are we aiming to support only the following platforms It'd be nice to also support |
upstream: amd64 only, though some Mac users have also requested downstream: amd64, s390x, ppc64le - check the release notes https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.8/html-single/release_notes_and_known_issues/index#supported-platforms re: go-toolset, I think you'll see arm64 IS supported: ![]() |
For the record I don't have a M1 Mac 😀 |
Just wanted to clarify some requirements for this:
Point 2. is slightly complicated by the fact that If any of my assumed requirements are incorrect, please correct me. |
…ct-clone images Fix devfile#559 Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
…ct-clone images Fix devfile#559 Signed-off-by: Andrew Obuchowicz <aobuchow@redhat.com>
RN status: upstream only |
Since CRW depends on DevWorkspace Operator it's needed to make sure it supports multiarch.
I assume it does not, since controller dockerfile does not have GO_ARCH, and project clone's one hardcodes amd64.
The text was updated successfully, but these errors were encountered: