-
-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when decrypting secrets on ArgoCD #158
Comments
Whats your local version of gpg? gpg --version Just to confirm, we are not hitting getsops/sops#896 |
First of all, thanks a lot for the fast response! Local: gpg (GnuPG) 2.3.3 So it really looks like that this is the issue :( Where is the dependency coming from on the ArgoCD image? Is my assumption right, that I'd have to create my own docker image in case I want to upgrade gpg? |
ArgoCD is using Ubuntu 21.04 as base. But eben Ubuntu 21.10 stays on gpg 2.2. You could try to use the gnupg packages from debian experimental to upgrade gpg inside the docker image. OR Do you have a chance to regenerate your gpg key? If yes, add |
I can confirm that the workaround with the --rfc4880 is working. Thanks a lot @jkroepke for helping out! |
Current Behavior
Error:
Error decrypting tree: Error walking tree: Could not decrypt value: crypto/aes: invalid key size 0
Full Error
Config:
Repo Server
Secret:
I verified that the key is mounted. Also the tools are mounted. If I execute a similar command as on ArgoCD locally, everything is working fine.:
helm upgrade abc-argo-cd . -f values.yaml -f 'secrets+gpg-import:///Users/abc/dev/misc/keys/key.asc?secrets.yaml' --namespace=argo-cd --create-namespace --install
Helm version on Argo is 3.6.0. On my local machine it is 3.7.1. Could it be a dependency issue?
Expected Behavior
The secret should be decrypted.
Steps To Reproduce
No response
Environment
Helm 3.6.0 on ArgoCD
Anything else?
No response
The text was updated successfully, but these errors were encountered: