build: gpg-agent run fix & automated login process
The gpg-agent could not start if the /root is mounted by docker when the external path is long enough, a workaround is to use a different GNUPGHOME for gpg key generation, and copy generated files to /root/.gnupg afterwards bonus: thanks to expect, we can a automated login process, if both PROTONMAIL_USERNAME and PROTONMAIL_PASSWORD are set Signed-off-by: Jeffrey Stoke <me@arhat.dev>
This commit is contained in:
parent
8fa301b5a3
commit
da0dfab9d3
6 changed files with 112 additions and 18 deletions
|
|
@ -6,3 +6,4 @@
|
|||
!gpgparams
|
||||
!Dockerfile
|
||||
!build.sh
|
||||
!login.exp
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue