[PR #551] [MERGED] Fix issue with invalid GPG keys in VNC version #783

New Issue

2025-12-29T06:22:51+01:00

adam commented

2025-12-29 06:22:51 +01:00

📋 Pull Request Information

Original PR: https://github.com/sickcodes/Docker-OSX/pull/551
Author: @aaronjamt
Created: 10/22/2022
Status: ✅ Merged
Merged: 11/10/2022
Merged by: @sickcodes

Base: master ← Head: patch-1

📝 Commits (1)

a43fc57 Fix issue with invalid GPG keys in VNC version

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 vnc-version/Dockerfile (+3 -0)

📄 Description

Without this, pacman gives the following errors when trying to update packages as part of the installation:

The first error is error: pambase: key "991F6E3F0765CF6295888586139B09DA5BF0D338" is unknown
This is followed by a bunch of errors similar to (but with different filenames): :: File /var/cache/pacman/pkg/pambase-20221020-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n]
These are followed by error: libvpx: key "95220BE99CE6FF778AE0DC670F65C7D881506130" is unknown
Finally, it ends with error: failed to commit transaction (invalid or corrupted package) and Errors occurred, no packages were upgraded. before exiting with code 1.

This RUN command will update the archlinux-keyring package to get the latest keys, then remove and regenerate all gnupg keys inside the container. This allows pacman to accept the GPG keys and resolves the above error.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sickcodes/Docker-OSX/pull/551 **Author:** [@aaronjamt](https://github.com/aaronjamt) **Created:** 10/22/2022 **Status:** ✅ Merged **Merged:** 11/10/2022 **Merged by:** [@sickcodes](https://github.com/sickcodes) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`a43fc57`](https://github.com/sickcodes/Docker-OSX/commit/a43fc57188f6f1f82bff0a5829c157ffed202e7f) Fix issue with invalid GPG keys in VNC version ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `vnc-version/Dockerfile` (+3 -0) </details> ### 📄 Description Without this, `pacman` gives the following errors when trying to update packages as part of the installation: * The first error is `error: pambase: key "991F6E3F0765CF6295888586139B09DA5BF0D338" is unknown` * This is followed by a bunch of errors similar to (but with different filenames): `:: File /var/cache/pacman/pkg/pambase-20221020-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n]` * These are followed by `error: libvpx: key "95220BE99CE6FF778AE0DC670F65C7D881506130" is unknown` * Finally, it ends with `error: failed to commit transaction (invalid or corrupted package)` and `Errors occurred, no packages were upgraded.` before exiting with code `1`. This `RUN` command will update the `archlinux-keyring` package to get the latest keys, then remove and regenerate all gnupg keys inside the container. This allows `pacman` to accept the GPG keys and resolves the above error. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

adam added the pull-request label 2025-12-29 06:22:51 +01:00

adam closed this issue

2025-12-29 06:22:51 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#783