Sometime last week, an attempted automated GitLab via Docker upgrade failed catastrophically, and left that Docker image in a pretty botched state. Kudos to the GitLab team for making it so many years without this being a problem. It was a real surprise to see it broken!
(more…)-
Self Hosted
It’s taken about-a-million tiny steps, but as of this moment (2 May, 2024 07:42 UTC-6) this WordPress blog (jjj.blog) and a bunch of other blogs for friends & family are all
(more…)calling from inside the houserunning on a cluster of Raspberry Pi 4’s in a server rack in my basement. -
Update GitLab signing key
At the beginning of April, GitLab updated their repository signing key. If you try to update, you will see an error during
sudo apt update:W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F W: Failed to fetch https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/dists/bionic/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F W: Some index files failed to download. They have been ignored, or old ones used instead.
The easiest fix appears to be simply to update the signing key:
curl --silent https://packages.gitlab.com/gpg.key | sudo apt-key add -
The trailing hyphen is part of the command; don’t forget it.