keybase / keybase/keybase-issues

Setup kbfs without redirector on a server without root access

Open
#3,809 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I am trying to run keybase on a server where I don't have root access. Following, https://keybase.io/docs/linux-user-guide#installing-keybase-without-root-privileges advice, I did the following:

mkdir src && cd src/
wget https://prerelease.keybase.io/keybase_amd64.rpm
rpm2cpio keybase_amd64.rpm | cpio -idmv
ln -s $HOME/src/usr/bin/keybase $HOME/bin
ln -s $HOME/src/usr/bin/run_keybase $HOME/bin
ln -s $HOME/src/usr/bin/kbfsfuse $HOME/bin

after doing the login,

run_keybase -g returns

WARNING: Expected the keybase executable to be /usr/bin/keybase, but it's
         /home/myuser/bin/keybase instead. Do you have multiple versions installed?
Export KEYBASE_PATH_WARNING=0 to silence this warning.
Launching keybase service...
Starting the redirector...
Starting KBFS...
run_keybase: Success!

KBFS failed to FUSE mount at /run/user/1012/keybase/kbfs: fusermount: exec: "fusermount": executable file not found in $PATH

It seems the mountdirdefault is /run/user/SOMENUMBER/keybase/kbfs, but KFBS is not running.

Is the problem that fusermount is missing or is it with redirector?

I can't edit /etc/keybase/config.json, but tried to edit ~/.config/keybase/config.json with

{
  "disable-root-redirector": true
}

~/.cache/keybase/keybase.redirector.log indicates:
nohup: failed to run command ‘keybase-redirector’: No such file or directory

What should I try (or read) next to mount kbfs?

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 non-root installation steps, the run_keybase -g output, and the ~/.cache/keybase/keybase.redirector.log entry. Check how the user-level config setting, fusermount lookup, and keybase-redirector path relate to the failed KBFS mount. Done means identifying the blocking requirement or configuration issue and documenting a reproducible non-root mounting path.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.