You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The official dockerfile uses ubuntu:22.04 as a base, which only has the command gpg and not gpg2.
load_gpg_key uses the gpg2 command and therefore can't load a gpg key with that setup.
You get a generic "Failed to read config file" error message once you try to add a build-gpg-key (weirdly gpg-key on repos doesn't throw an error).
I symlinked it to fix the issue for me (ln -s /usr/bin/gpg /usr/bin/gpg2), but it should get fixed in the dockerfile.
Side note:
The ubuntu image uses LC_ALL=C, which can make gpg throw a "A locale function failed" error if the key includes non-ASCII characters (for example in the uid name). Exporting keys still works, so it's not a problem.
The text was updated successfully, but these errors were encountered:
The official dockerfile uses ubuntu:22.04 as a base, which only has the command gpg and not gpg2.
load_gpg_key uses the gpg2 command and therefore can't load a gpg key with that setup.
You get a generic "Failed to read config file" error message once you try to add a build-gpg-key (weirdly gpg-key on repos doesn't throw an error).
I symlinked it to fix the issue for me (
ln -s /usr/bin/gpg /usr/bin/gpg2
), but it should get fixed in the dockerfile.Side note:
The ubuntu image uses LC_ALL=C, which can make gpg throw a "A locale function failed" error if the key includes non-ASCII characters (for example in the uid name). Exporting keys still works, so it's not a problem.
The text was updated successfully, but these errors were encountered: