Description of problem:

Client is creating Ansible workspace in dev-space 3.17 where they  need to set a GPG key to commit in their  repo. When they try to create a GPG key  the "error: error No pinentry" error is reported.

Prerequisites (if any, like setup, operators/versions):

Red Hat OpenShift Dev Spaces: 3.17

Steps to Reproduce

1. Launch the workspace: Ansible 
then run ;
gpg --gen-key

2. After entering your name and e-mail you will have the error:
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry

Actual results:

gpg creation results in following error:

gpg: key D79: error sending to agent: No pinentry

gpg: error building skey array: No pinentry

gpg: error reading 'myprivatekeys.asc': No pinentry

gpg: import from 'myprivatekeys.asc' failed: No pinentry

Expected results:

GPG key creation should proceed 

Additional info (Such as Logs, Screenshots, etc):

sh-4.4$ pwd
/projects
sh-4.4$ gpg --gen-key
gpg (GnuPG) 2.2.20; Copyright (C) 2020 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

gpg: directory '/home/user/.gnupg' created
gpg: keybox '/home/user/.gnupg/pubring.kbx' created
Note: Use "gpg --full-generate-key" for a full featured key generation dialog.

GnuPG needs to construct a user ID to identify your key.
 
Change (N)ame, (E)mail, or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry
sh-4.4$