[GH-ISSUE #1314] fuse: device not found, try 'modprobe fuse' first #703

New issue

Closed

opened 2026-03-04 01:48:03 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:48:03 +03:00

Owner

Originally created by @prasad-1729 on GitHub (Jun 22, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1314

Error message

fuse: device not found, try 'modprobe fuse' first
[CRT] set_s3fs_log_level(250): change debug level from [CRT] to [INF]
[INF] set_moutpoint_attribute(4088): PROC(uid=0, gid=0) - MountPoint(uid=1000, gid=1000, mode=40755)

Version of s3fs being used (s3fs --version)

_example: V1.86

s3fs command line used, if applicable

sudo s3fs buckect1 ./opt1 -o url=https://s3.us-south.cloud-object-storage.appdomain.cloud -o passwd_file=/home/jenkins/.passwd-s3fs -o ibm_iam_auth -o dbglevel=info -f -o curldbg

I am running in jenkinsfile(linux containers)
Thank!!!

Originally created by @prasad-1729 on GitHub (Jun 22, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1314 ### Error message fuse: device not found, try 'modprobe fuse' first [CRT] set_s3fs_log_level(250): change debug level from [CRT] to [INF] [INF] set_moutpoint_attribute(4088): PROC(uid=0, gid=0) - MountPoint(uid=1000, gid=1000, mode=40755) #### Version of s3fs being used (s3fs --version) _example: V1.86 #### s3fs command line used, if applicable ``` sudo s3fs buckect1 ./opt1 -o url=https://s3.us-south.cloud-object-storage.appdomain.cloud -o passwd_file=/home/jenkins/.passwd-s3fs -o ibm_iam_auth -o dbglevel=info -f -o curldbg ``` I am running in jenkinsfile(linux containers) Thank!!!

kerem closed this issue

2026-03-04 01:48:03 +03:00

kerem commented

2026-03-04 01:48:04 +03:00

Author

Owner

@lionelyoung commented on GitHub (Jun 22, 2020):

You need to enable privileges

On kubernetes, it'd be something like:

      containers:
        - name: xxx
          imagePullPolicy: IfNotPresent
          image: xxx
          securityContext:
            privileged: true
            capabilities:
              add:
                - SYS_ADMIN

With docker flags, you'd need to get something like:

--privileged --cap-add=SYS_ADMIN --device=/dev/fuse

@lionelyoung commented on GitHub (Jun 22, 2020): You need to enable privileges On kubernetes, it'd be something like: ``` containers: - name: xxx imagePullPolicy: IfNotPresent image: xxx securityContext: privileged: true capabilities: add: - SYS_ADMIN ``` With docker flags, you'd need to get something like: ``` --privileged --cap-add=SYS_ADMIN --device=/dev/fuse ```

kerem commented

2026-03-04 01:48:04 +03:00

Author

Owner

@prasad-1729 commented on GitHub (Jul 5, 2020):

Thanks @lionelyoung

@prasad-1729 commented on GitHub (Jul 5, 2020): Thanks @lionelyoung

kerem commented

2026-03-04 01:48:04 +03:00

Author

Owner

@jonzerstyle commented on GitHub (Apr 5, 2024):

I had this issue when trying to use curlftpfs on buildroot. It was fixed by enabling CONFIG_FUSE_FS=y in the kernel config.

@jonzerstyle commented on GitHub (Apr 5, 2024): I had this issue when trying to use curlftpfs on buildroot. It was fixed by enabling CONFIG_FUSE_FS=y in the kernel config.