Client: setsockopt error using Bash on Ubuntu on Windows

Created on 8 Sep 2016 · 5Comments · Source: keybase/client

Hey guys !

I'm trying to get keybase CLI working on windows using Bash on Ubuntu on Windows. Unfortunately, I'm getting an error when I try and contact the API server.

ERROR dial unix /home/username/.config/keybase/keybased.sock: setsockopt: invalid argument

Do you think this is a Windows-related error ?

my log id: 0f1f9a08ebce4bb383b49d1c

Source

leoternoir

Most helpful comment

Btw, I found a workaround for until the fix is released. If you add the --standalone parameter, the client won't try to fork a helper daemon, therefore it doesn't need to try to create a socket to talk to that daemon.

Just put the following in your .bashrc file:

alias keybase="keybase --standalone"

crashsystems on 14 Nov 2016

👍3

All 5 comments

Huh, yeah, probably, I don't think we've tried that. CC @zanderz

cjb on 8 Sep 2016

I see you are running a Linux client in the new Windows ubuntu subsystem, and it has some kind of socket connection errors. It would be interesting to see why it isn't working, but in general this is not yet a supported configuration, due to the lack of graphical presentation system.

zanderz on 8 Sep 2016

I'm also experiencing this issue. I have some Node experience, so I'd be happy to help debug this issue if needed.

crashsystems on 2 Oct 2016

@crashsystems @zanderz @leoternoir @cjb This is fixed in the latest Slow ring release. I'm afraid you'll have to wait a bit to get that outside Insiders previews.