ARM64 Support

[RedstoneWizard08]

Is your feature request related to a problem? Please describe

I would like to have GitPod Self-Hosted support ARM64 machines, as I was trying to install it on a cloud-hosted VM and it won't run, due to exec format errors.

Describe the behaviour you'd like

GitPod will run as a kubernetes application on ARM64 machines.

Describe alternatives you've considered

None, as I have not found anything else that does what GitPod does and supports ARM64 machines for self-hosting.

Additional context

[wolf-yuan-6115]

Is your feature request related to a problem? Please describe

I would like to have GitPod Self-Hosted support ARM64 machines, as I was trying to install it on a cloud-hosted VM and it won't run, due to exec format errors.

Describe the behaviour you'd like

GitPod will run as a kubernetes application on ARM64 machines.

Describe alternatives you've considered

None, as I have not found anything else that does what GitPod does and supports ARM64 machines for self-hosting.

Additional context

Cloud server like Oracle Cloud is arm64, and Raspberry Pi is arm based too.

I would like to hosting gitpod on my own Raspberry Pi if gitpod support it.

[RedstoneWizard08]

Haha I'm on Oracle Cloud too

[ZCube]

Anyone interested in solving this issue?

I think this issue will be resolved by doing the following tasks.

0. Prepare an automated build environment that can build on ARM64.
1. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/workspace-images/tree/master/base
2. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/workspace-images/tree/master/full
3. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/gitpod/tree/main/dev/image
4. Create a distribution package for this URL. https://github.com/grpc/grpc-node/tree/master/packages/grpc-tools
5. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/minio
6. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/mysql
7. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/rabbitmq
8. Modify the Dockerfiles in the repository to recognize the architecture. https://github.com/gitpod-io/gitpod

And a lot of time to do this...

[wolf-yuan-6115]

Almost all CI support arm CPU

…

On Wed, Jan 26, 2022, 16:50 ZCube ***@***.***> wrote: Anyone interested in solving this issue? I think this issue will be resolved by doing the following tasks. 1. Prepare an automated build environment that can build on ARM64. 2. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/workspace-images/tree/master/base 3. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/workspace-images/tree/master/full 4. Modify the Dockerfile of this URL to be buildable. https://github.com/gitpod-io/gitpod/tree/main/dev/image 5. Create a distribution package for this URL. https://github.com/grpc/grpc-node/tree/master/packages/grpc-tools 6. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/minio 7. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/mysql 8. Replace the bitnami related chart in this URL with another one. https://github.com/gitpod-io/gitpod/tree/main/installer/third_party/charts/rabbitmq 9. Modify the Dockerfiles in the repository to recognize the architecture. https://github.com/gitpod-io/gitpod And a lot of time to do this... — Reply to this email directly, view it on GitHub <#7700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN4MEDGFTIVUAXK2V2446KLUX6YU7ANCNFSM5MLERCGA> . You are receiving this because you commented.Message ID: ***@***.***>

[ZCube]

@wolf-yuan-6115
Building with amd64 takes more than an hour.
Arm64 is expected to take more than 2 hours.
Can you recommend a CI that can be used for more than 2 hours for free?

[RedstoneWizard08]

GitHub Actions?

[RedstoneWizard08]

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration

- Workflow run time - Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.

[ZCube]

@RedstoneWizard08
Does GitHub Actions provide an arm64 builder? The build method using QEMU failed.

#14 [linux/arm64  9/10] RUN sudo echo "Running 'sudo' for Gitpod: success" &&     mkdir -p /home/gitpod/.bashrc.d &&     (echo; echo "for i in $(ls -A $HOME/.bashrc.d/); do source $HOME/.bashrc.d/$i; done"; echo) >> /home/gitpod/.bashrc
#14 0.119 sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
#14 ERROR: process "/bin/sh -c sudo echo \"Running 'sudo' for Gitpod: success\" &&     mkdir -p /home/gitpod/.bashrc.d &&     (echo; echo \"for i in \\$(ls -A \\$HOME/.bashrc.d/); do source \\$HOME/.bashrc.d/\\$i; done\"; echo) >> /home/gitpod/.bashrc" did not complete successfully: exit code: 1
------
 > [linux/arm64  9/10] RUN sudo echo "Running 'sudo' for Gitpod: success" &&     mkdir -p /home/gitpod/.bashrc.d &&     (echo; echo "for i in $(ls -A $HOME/.bashrc.d/); do source $HOME/.bashrc.d/$i; done"; echo) >> /home/gitpod/.bashrc:
: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
------

[RedstoneWizard08]

@ZCube it does. I've gotten Docker images to build for arm64.
https://github.com/opendocs-editor/docker/blob/main/.github/workflows/build-on-push.yml

[RedstoneWizard08]

https://askubuntu.com/questions/625540/suddenly-cant-run-sudo

[ZCube]

@RedstoneWizard08 I'm trying it, and it looks better than I thought.
https://github.com/ZCube/workspace-images/actions/runs/1752016640

[RedstoneWizard08]

@ZCube you need to change the IMAGE variable in the workflow

[RedstoneWizard08]

https://github.com/RedstoneWizard08/workspace-images
https://github.com/RedstoneWizard08/workspace-images/actions/runs/1752296053

[ZCube]

@RedstoneWizard08 Thanks.