keybase / keybase/client

Can't use mac CLI

Open
#8,739 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Hi.

When i try to call the CLI on my Mac, i get "keybase command not found"

I'm a n00b fixing things outside the OS GUI. I did try some stuff based on what i found, but still haven't been able to get it to work.

I've tried to create a sym link in /usr/local/bin, but when i call keybase, it gives me "-bash: /usr/local/bin/keybase: cannot execute binary file". I guess i'm doing something wrong.

When i copy keybase from the app-contents to /usr/local/bin and call keybase, i get "No app bundle: Unable to resolve bundle for valid path: /usr/local/bin/keybase; %!s()

▶ ERROR There were multiple errors: dial unix /Users/raoul/Library/Group Containers/keybase/Library/Caches/Keybase/keybased.sock: connect: no such file or directory; dial unix /Users/raoul/Library/Caches/Keybase/keybased.sock: connect: no such file or directory"

The reason i need the CLI is the following: on my Mac i have 2 volumes. On one i have an environment i can work on. When a new OS version is released, i install it on the other volume. When everything works, i switch to that volume for working, and if a new version of the OS is released, i repeat. So i always have a working environment i can switch back to. Now: on 1 volume i installed Keybase. Than i decided i want to try a newer OS, so i installed it and all apps, including Keybase. But on install, it wants me to connect to the device Keybase is already installed on. I can't, because it is on the same device, but another volume. I found in the CLI i can remove a device from my device list. But i can't get the CLI to work. So now i'm stuck.

Could the remove/add device be added to the Keybase web environment?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the macOS CLI installation and device-management paths described in the report, including the app bundle, symlink, and device removal flow. Reproduce the reported command-not-found and socket errors, then determine whether the requested web-based add/remove device capability belongs in this issue; done should include a documented or working path for the stated two-volume setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
cli, desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.