Open doublethink13 opened 3 years ago
Found a fix:
# check owner of current tty
gitpod ~ $ ls -la $(tty)
crw------- 1 root nogroup 136, 1 Sep 10 2021 /dev/pts/0
# if its not gitpod (or your current user), create a pseudoterminal where you are, in fact, the owner
gitpod ~ $ script /dev/null
# export the necessary variable so that gpg is aware of this pseudoterminal
gitpod ~ $ export GPG_TTY=$(tty)
The above is not necessary if using sops as root (sudo su
before trying to decrypt).
See GnuPG docs.
Before closing this issue, I would like to know why we are not the owners of the pseudoterminal being used and if the above has any concerns regarding security, etc.
Bug description
SOPS is not working in my custom image. I get the following error:
I had previously encrypted the file with no problems:
Steps to reproduce
Anything else?
I did not install
gpg
. I did install SOPS, like so:Here is my custom image Dockerfile.