[GH-ISSUE #365] s3fs 1.79 on server with selinux enabled #187

New issue

Closed

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

kerem commented

2026-03-04 01:43:05 +03:00

Owner

Originally created by @ngbranitsky on GitHub (Feb 16, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/365

What do I have to add to selinux configuration (RHEL 7.2) to allow s3fs v1.79 to start?
The program name?
The mount point?

Originally created by @ngbranitsky on GitHub (Feb 16, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/365 What do I have to add to selinux configuration (RHEL 7.2) to allow s3fs v1.79 to start? The program name? The mount point?

kerem closed this issue

2026-03-04 01:43:05 +03:00

kerem commented

2026-03-04 01:43:06 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 6, 2016):

I'm not ready how to set the terms of SELinux now.
I think that we will reference it if someone set s3fs for SELinux.
Regards

@ggtakec commented on GitHub (Mar 6, 2016): I'm not ready how to set the terms of SELinux now. I think that we will reference it if someone set s3fs for SELinux. Regards

kerem commented

2026-03-04 01:43:06 +03:00

Author

Owner

@lstellway commented on GitHub (Jan 30, 2019):

You can try running audit2allow to see if there are any rules you need to update:

audit2allow -a

@lstellway commented on GitHub (Jan 30, 2019): You can try running [`audit2allow`](https://linux.die.net/man/1/audit2allow) to see if there are any rules you need to update: ``` audit2allow -a ```

kerem commented

2026-03-04 01:43:06 +03:00

Author

Owner

@gaul commented on GitHub (Jun 25, 2019):

Please reopen if the suggested workaround does not address your symptoms.

@gaul commented on GitHub (Jun 25, 2019): Please reopen if the suggested workaround does not address your symptoms.