Dockerfile install fails with unable to find gpg for signature verification on AmazonLinux

TL;DR

For "ERROR: Unable to find gpg binary for signature verification": install the full package instead: sudo yum install --allowerasing gnupg2. Issue DopplerHQ/cli#451 (closed, 5 comments): The install script in a Dockerfile on amazonlinux:2023 failed with "ERROR: Unable to find gpg binary for signature verification" even with gnupg installed.

ERROR: Unable to find gpg binary for signature verification

Steps

1. Issue DopplerHQ/cli#451 (closed, 5 comments): The install script in a Dockerfile on amazonlinux:2023 failed with "ERROR: Unable to find gpg binary for signature verification" even with gnupg installed. A maintainer explained that AmazonLinux maps gnupg to the gnupg2-minimal package, which does not include gpgv, and the installer had switched from gpg to gpgv because newer gnupg defaults to keyboxd for key storage, which breaks the scripted keyring flags. The fix is to install the full gnupg2 package, and the reporter confirmed thanks.
2. If the doppler install script fails in a Dockerfile with unable to find gpg binary for signature verification on AmazonLinux, the problem is that amazonlinux maps gnupg to the gnupg2-minimal package, which lacks the gpgv binary the installer needs. Install the full package instead: sudo yum install --allowerasing gnupg2. Background: the installer switched from gpg to gpgv because newer gnupg versions default to keyboxd for key storage, which silently ignores the --no-default-keyring and --keyring flags the script relied on. gpgv is a small binary built specifically for signature verification and is not affected, which is why the installer requires it. Alternatively, install via the package manager following the RedHat/CentOS tab of the official CLI install docs.

When to use

Use this skill when you run into "Dockerfile install fails with unable to find gpg for signature verification on AmazonLinux".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

A maintainer explained that AmazonLinux maps gnupg to the gnupg2-minimal package, which does not include gpgv, and the installer had switched from gpg to gpgv because newer gnupg defaults to keyboxd for key storage, which breaks the scripted keyring flags.

In the GitHub issue gh:DopplerHQ/cli#451 (https://github.com/DopplerHQ/cli/issues/451), the problem reported was: Issue DopplerHQ/cli#451 (closed, 5 comments): The install script in a Dockerfile on amazonlinux:2023 failed with "ERROR: Unable to find gpg binary for signature verification" even with gnupg installed. A maintainer explained that AmazonLinux maps gnupg to the gnupg2-minimal package, which does not include gpgv, and the installer had switched from gpg to gpgv because newer gnupg defaults to keyboxd for key storage, which breaks the scripted keyring flags. The fix is to install the full gnupg2 package, and the reporter confirmed thanks. The verified resolution was: If the doppler install script fails in a Dockerfile with unable to find gpg binary for signature verification on AmazonLinux, the problem is that amazonlinux maps gnupg to the gnupg2-minimal package, which lacks the gpgv binary the installer needs. Install the full package instead: sudo yum install --allowerasing gnupg2. Background: the installer switched from gpg to gpgv because newer gnupg versions default to keyboxd for key storage, which silently ignores the --no-default-keyring and --keyring flags the script relied on. gpgv is a small binary built specifically for signature verification and is not affected, which is why the installer requires it. Alternatively, install via the package manager following the RedHat/CentOS tab of the official CLI install docs.