keybase / keybase/client

got the cli working by symlinking the .sock out of the container

Open
#12,575 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

```ln -s $HOME/Library/Group\ Containers/keybase/Library/Caches/Keybase/*.sock $HOME/Library/Caches/Keybase/``` made the CLI start working. GUI still says 'not logged in'. I can't get my system to a state where everything's happy, but I'll take the CLI over nothing.

**Edit:** Accidentally a \

my log id: 3e6c79dc5af2f3288e08471c

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the macOS setup using the reported Keybase socket paths and the symlink command, then inspect the CLI and GUI login behavior. Done means the CLI and GUI both recognize the logged-in state without requiring the socket symlink; the supplied log ID may help diagnose the failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
cli, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.