diff options
| author | Aaronjamt <[email protected]> | 2022-10-21 22:23:45 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2022-10-21 22:23:45 -0700 |
| commit | a43fc57188f6f1f82bff0a5829c157ffed202e7f (patch) | |
| tree | e3ff7f91532edb20f499dcd430a3b99f282f8252 /helm/templates/data-pvc.yaml | |
| parent | Merge pull request #538 from TartanLeGrand/master (diff) | |
| download | docker-osx-a43fc57188f6f1f82bff0a5829c157ffed202e7f.tar.xz docker-osx-a43fc57188f6f1f82bff0a5829c157ffed202e7f.zip | |
Fix issue with invalid GPG keys in VNC version
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.
Diffstat (limited to 'helm/templates/data-pvc.yaml')
0 files changed, 0 insertions, 0 deletions