Hello community, I need some help, please. I am trying to build a custom Collabora Online docker image, based on Debian. So, in debian:stable-slim I do: # apt-get update && apt-get -y install cpio tzdata libcap2-bin apt-transport-https gnupg2 ca-certificates curl ... ... ... # gpg --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys 0C54D189F4BA284D gpg: directory '/root/.gnupg' created gpg: keybox '/root/.gnupg/pubring.kbx' created gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 0C54D189F4BA284D: public key "Collabora Productivity " imported gpg: Total number processed: 1 gpg: imported: 1 Done # curl https://www.collaboraoffice.com/downloads/gpg/collaboraonline-release-keyring.gpg --output /usr/share/keyrings/collaboraonline-release-keyring.gpg % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1276 100 1276 0 0 10274 0 --:--:-- --:--:-- --:--:-- 10290 # echo "deb [signed-by=/usr/share/keyrings/collaboraonline-release-keyring.gpg] https://collaboraoffice.com/repos/CollaboraOnline/25.04-CODE/CODE-deb /" > /etc/apt/sources.list.d/collabora.list # # apt-get update Hit:1 http://deb.debian.org/debian stable InRelease Hit:2 http://deb.debian.org/debian stable-updates InRelease Get:3 http://deb.debian.org/debian-security stable-security InRelease [43.4 kB] Get:4 https://www.collaboraoffice.com/repos/CollaboraOnline/25.04-CODE/CODE-deb InRelease [1728 B] Get:5 https://www.collaboraoffice.com/repos/CollaboraOnline/25.04-CODE/CODE-deb Packages [952 kB] Fetched 997 kB in 1s (1312 kB/s) Reading package lists... Done # echo "deb [signed-by=/usr/share/keyrings/collaboraonline-release-keyring.gpg] https://collaboraoffice.com/repos/CollaboraOnline/24.04-CODE/CODE-deb /" > /etc/apt/sources.list.d/collabora.list # apt-get update Hit:1 http://deb.debian.org/debian stable InRelease Hit:2 http://deb.debian.org/debian stable-updates InRelease Hit:3 http://deb.debian.org/debian-security stable-security InRelease Get:4 https://www.collaboraoffice.com/repos/CollaboraOnline/24.04-CODE/CODE-deb InRelease [1728 B] Err:4 https://www.collaboraoffice.com/repos/CollaboraOnline/24.04-CODE/CODE-deb InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 0C54D189F4BA284D, which is needed to verify signature. Reading package lists... Done W: OpenPGP signature verification failed: https://www.collaboraoffice.com/repos/CollaboraOnline/24.04-CODE/CODE-deb InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 0C54D189F4BA284D, which is needed to verify signature. E: The repository 'https://collaboraoffice.com/repos/CollaboraOnline/24.04-CODE/CODE-deb InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Why is the behavior of version 24.04 and 25.04 repositories different? Do I need another key for 24.04 or is it compromised? I’m lost. With gpg signature check desactivated, I am able to install Collabora v.24.04, but this is not the expected behavior for me. Thank you

You’re not going crazy :slightly_smiling_face: and your Dockerfile logic is basically fine. What you’re seeing is a real difference in how the repositories are signed, not a problem on your side and not a compromised key. Recent Collabora repositories (25.04 and newer) were updated to follow modern Debian/Ubuntu best practices: Key lives in /usr/share/keyrings/*.gpg Repo uses signed-by=... No reliance on the global keyring Older repositories like 24.04-CODE were never fully migrated and are still effectively verified against the global apt trusted keyring, regardless of signed-by. So when apt checks 24.04-CODE, it looks for the key in the system keyring, doesn’t find it there, and fails verification.

[image] New repository signing keys News We have updated our PGP signing key for COOL and CODE .rpm and .deb packages to align with modern standards. This change is necessary as some recent Linux distributions have migrated to Sequoia-PGP for key and signature verification. Action required: Users will need to update the Collabora Online PGP key on their systems. This can be done using the following commands: On RPM based distros: wget -O repomd.xml.key https://collaboraoffice.com/repos/CollaboraOnline/CODE-rpm/repodata/repomd.xml.… https://www.collaboraonline.com/code/#learnmorecode

Collabora Online v.24.04 deb repo signature failure

Installation & Configuration

Topic		Replies	Views
Collabaora Online public key is not available User Support	3	1149	September 7, 2025
That old public key issue... https://www.collaboraonline.com/code/#learnmorecode User Support	4	55	October 25, 2026
OpenPGP check for package collaboraofficebasis-core-debuginfo failed Installation & Configuration	2	137	September 21, 2025
Repository PGP update User Support	2	403	June 23, 2025
New repository signing keys News	0	722	June 20, 2025

5 - 7 April 2027, Berlin, Germany

Collabora Online v.24.04 deb repo signature failure

Related topics