-
Notifications
You must be signed in to change notification settings - Fork 244
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
Red Hat CodeReady Containers on ppc64le architecture? #1356
Comments
The CRC is a great tool for development, and will be very good to be ported on ppc64le. |
@ticlazau refer to crc-org/snc#209. There is work being done to support ppc64le for snc. This means that a single node cluster can be created pretty easily in a libvirt environment. In fact we have tried it and it works successfully. As for CRC - i'm not sure what the exact use case would be. If the argument is that it provides a great development environment, snc can do the same as well. I mean sure it would be nice to have a minishift like environment for ppc64le/s390x, but CRC was mainly desgned with laptop environments in mind.I don't see a very strong argument for CRC on ppc64le/s390x. |
hello there- please reach out to me on slack (username: mick) or look me up in IBM directory and send an email if you'd like to further discuss this. I'm helping prashanth drive this multi-arch effort but would like to better understand the use case as well. |
At this point, I see |
@ticlazau @mtarsel This can be closed right, as crc-org/snc#209 was merged! or is there more to be done here? |
I'm ok with closing this out while we focus on snc for ppc64le. This specific issue could always be re-opened at a later time. @ticlazau if ok with you, close this out? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello,
has anyone been able to run Red Hat CodeReady Containers on ppc64le architecture (Power Server with or without GPUs?)
Thank you,
FM
The text was updated successfully, but these errors were encountered: