Possible to enable FUSE?

[alexgusevski]

I need to mount an s3 bucket inside my container. But it seems to not be possible as fuse seems to not be enabled.

My usecase requires a lot of read and writes, which are cached and optimized in mountpoint-s3 and what I currently use in my codebase, rearchitecting this to using boto3 will take a lot of work and be very slow for my end user

[th0m]

Hi @alexgusevski we have planned work for adding FUSE, we'll keep you posted.
cc @spahl

[alexgusevski]

Hello @th0m thank you for the response! Is there any rough timeline for this? Coming days/weeks or more like month / months?

[th0m]

Should be out in two weeks!

[alexgusevski]

That's great, will wait for that then, thank you

[alexgusevski]

@th0m Will sandboxes support FUSE out of the box when containers get them, or is that a separate timeline?

[whoiskatrin]

@th0m Will sandboxes support FUSE out of the box when containers get them, or is that a separate timeline?

we will make sure it's all coordinated and enabled ASAP on sandboxes side

[th0m]

FUSE support is available @alexgusevski here is an example: https://github.com/elithrar/fuse-on-r2

[DarthBenro008]

I tried running this exact project and followed documentation, but unfortunately the mount fails while testing locally:

here are the logs:

{"level":"info","module":"","version":"1.2.1","time":1764350848,"caller":"/home/runner/work/tigrisfs/tigrisfs/main.go:126","message":"Starting TigrisFS version"}
{"level":"info","module":"","bucketName":"wireframes","mountPoint":"/root/mnt/r2/wireframes","time":1764350848,"caller":"/home/runner/work/tigrisfs/tigrisfs/main.go:127","message":"Mounting"}
{"level":"info","module":"","uid":0,"defaultGid":0,"time":1764350848,"caller":"/home/runner/work/tigrisfs/tigrisfs/main.go:128","message":"Default uid=gid"}
{"level":"info","module":"","time":1764350848,"caller":"/home/runner/work/tigrisfs/tigrisfs/core/cfg/conf_s3.go:120","message":"env AWS_ACCESS_KEY_ID = <REDACTED>"}
{"level":"info","module":"","time":1764350848,"caller":"/home/runner/work/tigrisfs/tigrisfs/core/cfg/conf_s3.go:125","message":"command line endpoint: https://<REDACTED>.r2.cloudflarestorage.com"}
/bin/fusermount: fuse device not found, try 'modprobe fuse' first
{"level":"fatal","module":"","error":"Mount: mount: running /bin/fusermount: exit status 1","time":1764350850,"caller":"/home/runner/work/tigrisfs/tigrisfs/main.go:158","message":"Mounting file system failed"}
Starting server on :8080
2025/11/28 17:27:31 Server listening on :8080

Error line:

/bin/fusermount: fuse device not found, try 'modprobe fuse' first

This is run on a MacOS M-series Chipset. Online debugging says to enable SYS_ADMIN or run it as previlaged mode, but i cannot pass both these variables as wrangler orchestrates these containers, any help would be appreciated!

[DarthBenro008]

On quick debugging, i was able to get it running by building the docker image separately and running it with:

docker build . -t fuse:latest
docker run -p 8080:8080 --privileged fuse:latest

I assume the production containers in cloudflare runs on privileged mode with isolation and wranger dev doesn't support running these containers in privileged mode nor there is a way to pass them as option. So i believe this is more of a wrangler issue