[RunPod] FUSE mount fails inside Docker container - /dev/fuse: operation not permitted
#8.592 aberto em 15 de jan. de 2026
Métricas do repositório
- Stars
- (4.859 stars)
- Métricas de merge de PR
- (Mesclagem média 2d 23h) (146 fundiu PRs em 30d)
Description
Environment
- SkyPilot version: 0.11.1
- Cloud provider: RunPod
- Container runtime: Docker (RunPod default)
Description
When launching a SkyPilot job on RunPod using a Docker image, the setup script fails to mount JuiceFS inside the container due to missing FUSE device permissions.
Error Logs
(setup pid=3732) 2026/01/15 04:39:08.698391 juicefs[5320] : The mount point is not ready in 10 seconds (mount process is not started yet), please check the log (/var/log/juicefs.log) or re-mount in foreground [checkMountpoint@mount_unix.go:249]
Dig into /var/log/juicefs.log, show following error logs:
2026/01/15 04:02:15.348704 juicefs[5420] : setpriority: permission denied [Serve@fuse.go:454] 2026/01/15 04:02:15.348968 juicefs[5420] : mknod /dev/fuse: operation not permitted [ensureFuseDev@device_linux.go:35] /usr/bin/fusermount: fuse device not found, try 'modprobe fuse' first 2026-01-15 04:02:15.352109 I | mount: fusermount exited with code 256 2026/01/15 04:02:15.352167 juicefs[5420] : fuse: fuse: fusermount exited with code 256 [mountMain@mount_unix.go:1056]
Expected Behavior
JuiceFS should mount successfully inside the Docker container. The same docker image and task yaml file works on AWS instances.
Workaround Attempts
- Installing fuse package in Dockerfile - Doesn't help, as the issue is runtime permissions, not missing binaries
- Using --privileged in docker run options - Still fails due to missing device and capabilities