-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
ARM64 builds? #3505
Comments
Please help to do investigation if we can support ARM64 build. Thanks. |
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. |
Yes, I would like to see an arm64 build of harbor! |
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. |
For reference, my first attempt at this is documented in #6277 . |
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. |
So how things progress? Does harbor support ARM64 build now? |
Does harbor support ARM64 build now? Does harbor support ARM64 build now? |
@steven-zou I was blocked on porting harbor to aarch64 platfrom with the problem of registry-photon, which is only offering x86 version. Can you send me an arm64v8 version, because I notice that your collegaue Yang Wang is responsible for the Dockerfile of registry-photon module. Thanks! |
@congweitao any progress on this ? |
I compiled it on ARM64 server succussfully. I uploaded it to dockerhub, see docker pull congweitao/registry-photon:v2.7.1 |
@congweitao nice to hear that! what's left to do to get it up and running ? I'm here with a 6 node RPI 4B k3s cluster and want to see this working via the helm chart of harbor: |
All components are now running normally. The most important is to change photon:2.0 to photon:3.0, and the Dockerfiles have to be modified in order to compile successfully. I uploaded the docker images to dockerhub too. |
@congweitao may I don't get it, but which images exactly are you referring to ? |
push |
FYI |
I need arm64 harbor , where can I get it? |
Hi guys, if some one is interested I created a very simply workaround here: https://github.com/robyrobot/rosettak8s. |
https://github.com/octohelm/harbor has cross-built harbor images. Working great on rpi. |
Would love to see official arm64 support in the future |
I need to run Harbor on an ODROID M1, which uses a Rockchip RK3568B2 CPU (quad-core ARM Cortex A55), and has 8 GB of RAM. I'm running Ubuntu Server 22.04 LTS 64-bit with Podman, because the version of iptables isn't compatible with Docker, for some odd reason. Is there an arm64 image available for Harbor? |
I need arm64 harbor , where can I get it? |
hi do you have any idea that can get arm harbor ? |
We have verified this harbor arm64 build patch by @morlay works v2.8.3...morlay:harbor:patch-v2.8.3. |
hi thanks, i have solved that problem. I can rebuild the arm image on the arm machine. there are official ways to do that. besides there are also already pushed arm images on the docker hub for the public. so that I can easily docker pull the arm images. |
This does not work for all architectures, but at least amd64 and arm64. I could also add a switch statement, but ARM64 seems to be the most important arch to implement right now (goharbor#3505).
This does not work for all architectures, but at least amd64 and arm64. I could also add a switch statement, but ARM64 seems to be the most important arch to implement right now (goharbor#3505). Signed-off-by: Aaron Dewes <aaron.dewes@protonmail.com>
Any advances with this issue??, @morlay patch works very well but its not an official solution, the official solution arm-harbor seems discontinued |
Hi All,
In this day and age, lots (if not most) golang based projects also provide ARM64 builds. Would you consider doing one also please?
The text was updated successfully, but these errors were encountered: