keybase / keybase/client

[Docker] KBFS failed to FUSE mount /dev/fuse: no such file or directory

Open
#16,182 10 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

Hello,
I'm facing with problem while trying to use kbfs in docker container.
Here is a Dockerfile (copied from https://hub.docker.com/r/langrisha/keybase/dockerfile with just one change dpkg -i keybase_amd64.deb 2> /dev/null || true ):

FROM thyrlian/android-sdk:latest # ->FROM ubuntu:16.04

RUN \
	# Install dependencies
	apt-get update && apt-get install -y \
		curl \
		fuse \
		libappindicator1 \
		--no-install-recommends \

	# Get and verify Keybase.io's code signing key
	&& curl https://keybase.io/docs/server_security/code_signing_key.asc | \
		gpg --import \
	&& gpg --fingerprint 222B85B0F90BE2D24CFEB93F47484E50656D16C7 \

	# Get, verify and install client package
	&& curl -O https://prerelease.keybase.io/keybase_amd64.deb.sig \
	&& curl -O https://prerelease.keybase.io/keybase_amd64.deb \
	&& gpg --verify keybase_amd64.deb.sig keybase_amd64.deb \
	&& dpkg -i keybase_amd64.deb 2> /dev/null || true \
	&& apt-get install -f -y \

	# Create group, user
	&& groupadd -g 1000 keybase \
	&& useradd --create-home -g keybase -u 1000 keybase \

	# Cleanup
	&& rm -r /var/lib/apt/lists/* \
	&& rm keybase_amd64.deb*


USER keybase
WORKDIR /home/keybase
CMD ["bash"]

when I run run_keybase as keybase user I get

Launching keybase service...
Starting the redirector...
Starting KBFS...
Launching Keybase GUI...
run_keybase: Success!
                                                  ▄▄▄▄█▀    
╭───────────────────────╮          ▄▄          ▄▄▄█▄▄▀      
│                       │         ███▄▄▄▄▄▄▄▄▄▄███▄██       
│  Encrypt everything!  │       ▄▄▄████▄▄▄███████████       
│                       ├────  ▄▄▄▄▄████▄█████████████      
╰───────────────────────╯      ███▄█▄█████████████████▄▄    
                                ▀▄███████▄▀ ███████████▄▄   
                                  ▄▄▄▄███    ███████████▄▄  
                                 ▄████████   ██████████████ 
                                ▄███▄█████▄▄  ▀▄████████████
                               ███████▄▄██▄█▄▄ █████████████
                              ▄▄█████████████▄▄ ████████████
                           ▄██▄▄████▄▄▄█▄▄█████ ████████████
                                ███▄▄▄▄▄███████▄▄█████████▄▀
                                ▄█████▄▄█████████████▄█████ 
                                █▄██████████▄▄▄▄▄▄▄███████  
                              ▄▄▄▄▄██▄▄█████▄████████████   
                            ▀▀▀▀▀▀▀▀▄▄▄▄██▄▀ ▀▀▄▄▄▄▄▄▀▀▀    
                                  ▀▀▀▀▀▀▀▀▀                 

keybase@fe9ddd5d307b:~$ KBFS failed to FUSE mount at /home/keybase/.config/keybase/kbfs: fusermount: exit status 1

when I run it as root # KEYBASE_ALLOW_ROOT=1 run_keybase it prints the same error

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 with the provided Dockerfile and the run_keybase invocation, then inspect the KBFS FUSE mount failure involving /dev/fuse. Reproduce the failure in the described container and determine the supported container setup or required change; done means the mount works or the limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, 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.