keybase filesystem showing up as "not running" (even though it is, I think)

[sbromberger]

seth@schroeder:~$ keybase status
Username:      sbromberger
Logged in:     yes

Device:
    name:   schroeder
    ID:     ede3703d21796ecb22e6f026671c8318
    status: active

Local keybase keychain: unlocked
Session status:         sbromberger [loaded: yes, cleared: no, expired: yes]

KBFS:
    status:    not running
    version:   1.0.0-20160215170048+d9662a2
    log:       /Users/seth/Library/Logs/keybase.kbfs.log

Service:
    status:    running
    version:   1.0.11-20160215170009+d9662a2
    log:       /Users/seth/Library/Logs/keybase.service.log

Platform Information:
    OS:        darwin
    Runtime:   go1.5.3
    Arch:      amd64

Client:
    version:   1.0.11-20160215170009+d9662a2

Desktop app:
    status:    running
    log:       /Users/seth/Library/Logs/Keybase.app.log

Config path:        /Users/seth/Library/Application Support/Keybase/config.json
Default user:       sbromberger
Provisioned users:

command-line client(s):
    keybase status [pid: 52862, version: 1.0.11-20160215170009+d9662a2]

desktop(s):
    /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=2 --enable-zero-copy --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=51596.1.1750335714 [pid: 51599, version: 1.0.11-20160215170009+d9662a2]
    /Applications/Keybase.app/Contents/MacOS/Electron [pid: 51596, version: 1.0.11-20160215170009+d9662a2]
    /Applications/Keybase.app/Contents/Frameworks/Keybase Helper.app/Contents/MacOS/Keybase Helper --type=renderer --no-sandbox --lang=en-US --node-integration=true --num-raster-threads=2 --enable-zero-copy --content-image-texture-target=3553,3553,3553,3553,3553,34037,3553,3553,3553,34037,3553,34037,34037 --video-image-texture-target=34037 --channel=51596.2.1161101181 [pid: 51601, version: 1.0.11-20160215170009+d9662a2]

KBFS(s):
    /Applications/Keybase.app/Contents/SharedSupport/bin/kbfs -debug /keybase [pid: 47338, version: 1.0.0-20160213170046+d9662

my log id: d74a6d010b7ecc5338de6b1c

[strib]

@maxtaco: I've noticed this before too. You can see the bottom KBFS(s) showing that KBFS sent the right HelloIAm call, but why does the upper section list it as "not running"?

[RyanSinger]

I just had this issue on ubuntu.

[maxtaco]

Known bug! We have it in this sprint to fix.

On Friday, February 19, 2016, Ryan Singer notifications@github.com wrote:

I just had this issue on ubuntu.

— Reply to this email directly or view it on GitHub https://github.com/keybase/client/issues/2031#issuecomment-186446253.

[vitoc]

This is still not working for me. Quite sure KBFS is actually not running.

This is on an Ubuntu container bootstrapped as such:

RUN apt-get update && apt-get install -y --no-install-recommends \ apt-transport-https \ libappindicator1 \ fuse \
curl \ sudo \ ca-certificates \
&& curl -O https://prerelease.keybase.io/keybase_amd64.deb \ && sudo dpkg -i keybase_amd64.deb \ && run_keybase && adduser --disabled-login --home $HOME --gecos "" brain \ && chown -R brain:brain $HOME

[strib]

@vitoc: can you please do a keybase log send and tell us the log ID? (Might be better in a new issue -- this one is super old and the issue is likely very different.)

Note that you need to run run_keybase as the same Unix user you will be accessing the files as. Looks like you made brain after you ran run_keybase.

[vitoc]

Thanks @strib , here's the Log ID: 2adef5629508c9ccf686781c

[strib]

@vitoc: looks like your user doesn't have permission to read /dev/fuse:

4 2016/08/13 06:20:09 mount helper error: fusermount: failed to open /dev/fuse: Operation not permitted
5 2016/08/13 06:20:09 mount helper error: fusermount: failed to open /dev/fuse: Operation not permitted
6 kbfsfuse error: (2) fusermount: exit status 1

Check out the permissions on that device and make sure your user is in the appropriate group.

Although I just remembered you're running in a container -- you may need to be in -privileged mode for fuse to work within the container.

[vitoc]

Thanks @strib . Got it now. Here's the working container: https://github.com/vitoc/ContainerPC