/keybase not created, fuse not mounting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I installed keybase for arch linux using the recommended yaourt instructions, but the KBFS was not created nor mounted. ls shows now keybase in / . I can't access keybase encrypted things or keybase public things. I tried reinstalling and executing run_keybase again, but even though the ANSI squirrel says "mounting /keybase" the opposite has happened.
my log id: 87ab8c64e174c58aeb11d81c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the Arch Linux installation instructions and the run_keybase entry point, then inspect the KBFS mount setup for /keybase using the supplied log ID. Done means KBFS is created and mounted so both Keybase encrypted and public content can be accessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, go, 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