Open Soupala opened 9 years ago
Run mkdir /root/.gnupg
as root. (Since it looks like you're running keybase as root.) The issue is that gpg sometimes creates that directory for itself and sometimes refuses to. We should probably just do it on startup -- it seems to be a frequent issue for people. Any objections, @maxtaco?
I had this problem too. I ended up running gpg --gen-key
after realising the issue. I was going to suggest the same as @oconnor663 - If it's possible to do this during keybase-installer
while properly init'ing gpg (if there are any other init steps that gig needs).
I think enough of an edgecase where its not a big deal either way. As long as others can query and find this answer/solution.
[ {name : "Mica Cardillo"} , {phone : "541.840.7245"}, {love: ['Dahlia', 'Oliver', 'Rachel']} ]
On Wed, Sep 9, 2015 at 1:24 AM, mattjbones notifications@github.com wrote:
I had this problem too. I ended up running gpg --gen-key after realising the issue. I was going to suggest the same as @oconnor663 https://github.com/oconnor663 - If it's possible to do this during keybase-installer while properly init'ing gpg (if there are any other init steps that gig needs).
— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/1729#issuecomment-138822581 .
+1 Ran into this myself. However, I was not running keybase as root.
mkdir /[path]/.gnupg
as normal user (h/t @oconnor663) worked for me.
Thanks!
I installed the prerequisites on Ubuntu 14.04 with 'apt-get install gnupg', although I think it comes preinstalled.
root@hostname:/# keybase version keybase (keybase.io CLI) v0.8.16
root@hostname:/# keybase login info: Updated file: /root/.cache/keybase/session.json error:
gpg
exited with code 2 warn: gpg: keyblock resource/root/.gnupg/secring.gpg': file open error warn: gpg: keyblock resource
/root/.gnupg/pubring.gpg': file open error warn: gpg: fatal: /root/.gnupg: directory does not exist! warn: secmem usage: 0/0 bytes in 0/0 blocks of pool 0/65536