gitlab@mycompany-gitlab01:~$ curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5933 100 5933 0 0 7406 0 --:--:-- --:--:-- --:--:-- 7406
Detected operating system as Ubuntu/focal.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/gitlab_gitlab-ce.list...done.
Importing packagecloud gpg key... done.
Running apt-get update... done.
The repository is setup! You can now install packages.
gitlab@mycompany-gitlab01:~$ sudo EXTERNAL_URL="https://gitlab.mycompany.com" apt-get install gitlab-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package gitlab-ce
gitlab@mycompany-gitlab01:~$
NEVER do curl | sh style commands! You don’t know what you’re executing. It only gets worse whenyou add sudo to the mix.
A lot of documentation online tells you to, but it’s a terrible idea. The way around it is to download the script, inspect it and execute the downloaded and inspected copy. (the download might change between two downloads, so it has to be the downloaded copy you execute).
The output from apt-get update suggests that the gitlab repository hasn’t been added. Can you show us the complete output from the setup script?
You’re seeing this error because we’ve yet to release gitlab-ce and gitlab-ee packages for Ubuntu 20.04 focal foss.
Right now the issue has a milestone of 13.2, which suggests the packages will be available on or before the GitLab 13.2 release scheduled for July 22nd.
In the meantime, there are two workarounds to install the 18.04 package(s) on 20.04 until the official package is made available:
Note in both cases the workarounds examples use the gitlab-ee repository.
For gitlab-ce packages, replace all references to gitlab-ee with gitlab-ce in the example commands if using these workarounds…