Ubuntu server 20.04 on raspberry pi: Unable to locate package gitlab-ce

Hi!
I’m trying to install gitlab-ce on my raspberry pi 3 (as a crash test before installing it on my rpi 4).

Here are the steps I followed:

• sudo apt update
• sudo apt upgrade
• sudo apt install curl openssh-server ca-certificates
• sudo apt install postfix
• curl https://packages.gitlab.com/gpg.key | sudo apt-key add -
• sudo curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
• sudo apt install gitlab-ce

I got: E: Unable to locate package gitlab-ce

I have a fresh install of ubuntu server 20.04 on a raspberry pi 3 with : Kernel: 5.4.0-1013-raspi aarch64 bits: 64, System: Raspberry Pi 3 Model B Rev 1.2, System: Raspberry Pi 3 Model B Rev 1.2, CPU: arch: ARMv8.

Gitlab for ubuntu focal fossa was released so it’s supposed to work. I tried this: https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5176#note_352351367 but got the same error.

Thanks for your help

Hello @Izaya,

The RPi repository is here: https://packages.gitlab.com/gitlab/raspberry-pi2

Installation instructions:

What might be important for you is the warning that you may find there:
" Raspberry Pi 4 with at least 4GB is recommended. Only 32bit ( armhf ) is supported at this point. 64 bit ( aarch64 ) is on its way."

Best Regards,
Łukasz Korbasiewicz
Support Engineer
GitLab, Inc.

Thank you for this fast answer. I thought I need the Ubuntu package because my OS isn’t Raspbian.

I tried it on the rpi 3 but it gave me the same error. Perhaps because it’s a rpi 64 bits (aarch64) and, as you pointed out, it’s not currently supported.
So I will wait for this release.

Have a nice day!
Izaya

Hi… On the off chance that you update Ubuntu, another vmlinuz is added to the boot index, and the former one is gone to vmlinuz.bak.
What you have to do is rename your vmlinux decompressed picture to vmlinux.bak (or erase it), take the new vmlinuz picture and decompress it as expressed previously.

When you are utilizing the refreshed and decompressed picture, it will boot without issue.

Ubuntu will consistently refresh on the principal boot. On the off chance that you leave it running long enough, a quiet update measure runs out of sight. I had a similar issue, and it took some effort to sort it out.

It comes down to the way that it is anticipating that you should boot utilizing u-boot which will decompress a compacted bit. The ordinary raspberry pi bootloader won’t acknowledge a packed picture, so it can’t boot. Any time you do an update, you simply need to decompress the new part picture and all that will fill in true to form.